Does the collector offline alert fire repeatedly while collectors remain offline?
Normally, the alert does not create a new alert cycle while the same collector remains offline. The alert clears when the collector reconnects and resumes normal communication. If the collector later goes offline again, the alert can trigger again according to its configured conditions and notification settings.
Repeated notifications may also be affected by repetitive-alert pause settings, notification frequency, or suppression rules.
Why did the collector offline alert clear even though I didn’t fix anything?
The alert clears when the collector resumes communication with the Auvik cloud. A brief DNS, proxy, firewall, or network interruption may have resolved without any manual change.
If the alert clears unexpectedly, ask your collector or network administrator to review the collector status and relevant network, DNS, proxy, and firewall logs around the time of the alert.
See this article for additional information: What happens if my collector disconnects?
Can I reduce false positives without missing real collector issues?
Yes. Review the alert’s detection window, offline-duration threshold, or alert delay and increase it slightly if brief interruptions are expected in your environment.
You can also use maintenance windows for planned work and confirm that the collector host has stable network, DNS, proxy, and time synchronization.
Changes to collector infrastructure, DNS, proxy, firewall, or NTP settings should be performed by an authorized administrator. Do not increase the alert delay so much that a sustained collector outage goes unnoticed.
For critical environments, consider configuring an additional collector that can reach the same networks and devices. A standby collector only provides failover if it is online and has the required network visibility.
What if only some sites went offline, not all of them?
Review the alert scope and the collectors assigned to the affected sites.
A tenant-wide or organization-level alert may evaluate all collectors within its configured scope. A site-level alert evaluates only the collectors included for that site. If you need visibility for individual sites, create or configure site-scoped alerts in Alerts v2.
Also confirm whether the affected sites use a shared collector. A single shared-collector outage can affect multiple sites and may generate separate notifications depending on the alert scope and notification configuration.
See this article for information about reducing duplicate notifications: Reduce shared collector disconnected alert noise
We moved to Alerts v2 but still see collector offline alert noise. What should we check?
Confirm that the Alerts v2 collector offline alert is enabled, scoped to the intended collectors or sites, and associated with the correct notification channels.
If the Legacy equivalent is still enabled, disable it or remove its notification channels to prevent duplicate notifications. Also review notification-channel associations, alert delays, repetitive-alert pause settings, maintenance windows, and suppression rules.
If noise continues, ask your collector or network administrator to investigate intermittent DNS, proxy, firewall, or network connectivity issues. These environmental issues can cause a collector to disconnect and reconnect even when it appears healthy later.
See this article for information about the alert itself: Auvik collector disconnected alert