Automatically Clear Informational Alerts Using Alerts v2

Alerts v2 can automatically clear informational alerts when a recovery condition is met or after a configured duration. This helps prevent informational events from remaining open and reduces the need to dismiss them manually.

How automatic clearing works

An Alerts v2 alert can clear automatically when:

• The monitored condition returns to normal.
• A custom clear condition is met.
• An Auto Clear period expires, when available.

If an alert does not have a clear condition or Auto Clear setting, it may need to be dismissed manually.

Migrating an alert from legacy alerting

If you are replacing a legacy informational alert:

1. Review the existing alert’s trigger condition, scope, severity, and notification settings.
2. Disable the legacy alert to prevent duplicate notifications during testing.
3. Recreate the alert in Alerts v2 with the required scope and trigger condition.
4. Configure a clear condition or Auto Clear setting.
5. Test the Alerts v2 alert using a safe, non-production condition.
6. Disable or remove the legacy alert after the Alerts v2 version is confirmed.

Create an automatically clearing alert

1. Go to Alerts > Manage alerts.
2. Create a new alert or open an existing Alerts v2 alert.
3. Define the alert scope, such as devices, interfaces, services, groups, or tags.
4. Configure the trigger condition.
5. Set the severity to Informational, if appropriate.
6. Configure the clear behavior:
   • Use the default inverse of the trigger condition.
   • Create a custom clear condition that defines the recovery state.
   • Use Auto Clear, when available, to resolve the alert after a specified period.
7. Add the appropriate notification channels.
8. Add a clear message if one is available for the alert type.
9. Save the alert.

Examples of clear conditions include:

• CPU usage remains below 70% for a defined period.
• A service returns to a running state.
• A monitored value returns below its trigger threshold.
• No matching event is detected during the configured clear period.

Test the alert

Use a non-production device or a safe test condition whenever possible.

1. Trigger the alert condition.
2. Confirm that the alert and notification are generated.
3. Restore the monitored condition.
4. Confirm that the clear condition is met.
5. Verify that the alert changes to a resolved or cleared state.
6. Confirm that notifications are not duplicated by a remaining legacy alert.

Troubleshooting

The alert does not clear

• Confirm that the clear condition uses the correct metric and scope.
• Verify that the recovery value meets the configured threshold.
• Check that the device or service is reporting current data.
• Review any alert delay or evaluation window.
• Confirm that the alert is not affected by a maintenance window, override, or suppression.

Duplicate notifications are generated

• Confirm that the legacy version of the alert is disabled.
• Check whether both alert definitions use the same scope and notification channel.
• Review parent and child site alert configurations for overlapping definitions.

The alert clears and triggers repeatedly

• Increase the trigger or clear delay.
• Use a wider difference between trigger and clear thresholds.
• Confirm that the monitored metric is not fluctuating around the threshold.

Alerts v2 is unavailable

• Confirm that Alerts v2 is enabled for the organization or site.
• Verify that your user role has permission to manage Alerts v2 definitions.
• Contact your Auvik administrator or Auvik Support if Alerts v2 is not available.

Related articles

• Creating Alerts using Alerts v2
• Managing Alerts using Alerts v2
• Setting Alerts v2 Trigger Conditions
• How to set Alert Delays with Alerts v2
• How to set Alert Delays on Clears with Alerts v2
• Creating Alert Notifications using Alerts v2
• Alerts v2 Permissions