In Alerts 2.0, an alert with a configured clear condition should clear automatically when that condition is met and the required evaluation period has completed.
An alert with a clear condition generally cannot be cleared manually. Dismissing a resolved event row only removes it from the active view; it does not force an active alert to clear.
1. Verify the clear-condition logic
Review the alert definition and confirm that:
- The clear condition uses the intended metric.
- The comparator is correct.
- The clear threshold can actually be reached.
- The clear condition applies to the same device, interface, service, or other entity scope as the trigger condition.
- The alert definition is enabled.
For example, if an alert triggers when utilization is greater than 80 percent, confirm that the clear condition is configured to clear when utilization falls below the intended value.
2. Check clear timing and persistence
Some alerts include a clear delay or other evaluation requirement. The clear condition may need to remain true for the configured period before Auvik marks the alert as cleared.
Review the alert’s clear-delay settings and allow time for the required health-check or metric-evaluation cycle to complete.
See How to set Alert Delays on Clears with Alerts v2.
3. Confirm that the source data is updating
Open the affected device, interface, service, or component and review the related metric or status history.
Confirm that:
- New data points are being received.
- The data reflects the expected clear state.
- The monitored entity is still online and correctly associated with the alert.
- There is no polling, credential, or collector issue preventing updated data from being collected.
Auvik may take a short period to confirm stable recovery before changing the alert to Resolved.
4. Check scope and notification settings
Confirm that the alert has not been changed or overridden at another level.
Review:
- Parent, multi-site, and site-level alert definitions.
- Device, interface, service, or tag scope.
- Alert enablement.
- Notification channels.
- Suppression rules and maintenance windows.
Suppression or maintenance settings may prevent notifications from being sent even though the alert event exists. Review the alert status in Auvik separately from the notification history.
5. Allow the alert to re-evaluate
After confirming the clear condition and source data, allow the next polling and evaluation cycles to complete. Refresh the alert view and check whether the alert has changed to Resolved.
Avoid temporarily changing a production threshold solely to force the alert to clear. If the alert remains active after the clear condition is visibly true and sufficient evaluation time has passed, contact Auvik Support.
Provide:
- Alert name or definition ID.
- Affected device, interface, service, or component.
- Trigger and clear conditions.
- Alert and clear-delay settings.
- Recent metric screenshots or timestamps.
- Site or tenant name.
- Approximate time the clear condition became true, including timezone.