When multiple child sites use the same Auvik collector, a single collector outage can generate a Collector Disconnected alert for each affected site. This can result in duplicate emails, PSA tickets, or other notifications.
Preferred method: group shared collector alerts in Alerts v2
Alerts v2 can group shared-collector disconnections so that one notification is generated from the parent multi-site instead of separate notifications for each child site.
To enable this option:
- Navigate to Manage Alerts > Alerts.
- Open the Alerts v2 tab.
- Locate the Auvik Collector Disconnected alert definition.
- Select the alert definition and click Edit.
- Under Trigger Conditions, locate Group Shared Collector Alerts.
- Select Only notify me once from the parent collector for any shared collectors.
- Review the alert definition and click Save.
When this option is enabled, a shared collector disconnection triggers once on the parent multi-site rather than separately for each site that uses the collector.
Important: Saving changes to an Alerts v2 definition can clear active alerts for that definition because the alert definition has changed.
Legacy alert workaround
If the environment uses legacy alerting, centralize collector monitoring at one designated site, typically the parent or multi-site level.
At the child sites:
- Review the Collector Disconnected alert.
- Disable the duplicate child-site collector alerts.
- Confirm that the parent or designated site retains the active collector health alert.
This ensures that one site is responsible for notifying on a shared collector outage.
Verify the configuration
After updating the alert configuration:
- Review the collector assignments and confirm which sites use the shared collector.
- Review the alert definition and confirm that the parent-only grouping or centralized monitoring is configured.
- Review the notification channels and confirm that the intended email, PSA, webhook, or other destination is associated with the alert.
- If testing is required, perform a controlled test during an approved maintenance window.
- Confirm that the parent or designated site receives the collector alert and that duplicate child-site notifications are not generated.
Do not intentionally disconnect a production collector unless the test has been approved and planned.
Important considerations
- The Alerts v2 grouping option applies to collector alert definitions.
- Legacy alerts require the parent-site centralization workaround.
- Some sites may still show status changes even when only one notification is sent.
- Notification-channel configuration can also create duplicate emails or tickets if multiple alert definitions use the same channel.
- A shared collector remains a dependency for every site it monitors. If the collector is unavailable, monitoring and data collection for those sites may be affected.