Primary Purpose: Notify when an Auvik collector has disconnected from the Auvik cloud and is no longer actively monitoring the network.
Alert Severity
Critical
Repetitive Alert Pause Condition
After 10 occurrences within 2 hours against a specific collector, the alert is automatically paused for 2 hours.
Alert Trigger Condition
An Auvik collector has been disconnected from the Auvik cloud for longer than the configured threshold and is considered offline.
Alert Clear Condition
The collector successfully reconnects to the Auvik cloud and resumes normal operation.
Why This Alert Matters
The collector is responsible for network discovery, monitoring, configuration backups, and communication with the Auvik cloud.
When a collector disconnects:
- Discovery stops.
- Device status information is no longer updated.
- Configuration backups stop running.
- TrafficInsights flow data collection stops.
- Syslog collection stops.
- New devices are not discovered.
- Alerting accuracy may be affected.
Existing data remains visible in Auvik, but it reflects the last known state of the network until the collector reconnects.
Common Causes
This alert can occur for several reasons:
Planned Maintenance
- Auvik is performing a collector upgrade.
- The collector host is undergoing maintenance.
- The collector has been intentionally shut down.
Infrastructure Issues
- The physical or virtual machine hosting the collector has powered off.
- The hypervisor hosting the collector is unavailable.
- A Windows or Linux collector host has restarted unexpectedly.
Network Connectivity Issues
- The collector has lost Internet connectivity.
- DNS resolution has failed.
- A firewall or security appliance is blocking communication with the Auvik cloud.
- A newly deployed proxy server is interfering with collector traffic.
Collector Issues
- The collector service has stopped.
- The collector installation has become corrupted.
- The collector operating system is no longer supported.
Recommended Actions
Step 1: Verify the Collector Host
Confirm that the device running the collector is powered on:
- VMware virtual appliance
- Hyper-V virtual machine
- Windows collector host
- Linux collector host
- Docker deployment
If the host is powered off, start it and verify that the collector reconnects.
Step 2: Verify Network Connectivity
Confirm the collector can:
- Reach the Internet
- Resolve DNS names
- Communicate with the Auvik cloud
Review any recent firewall, proxy, or routing changes that may be affecting connectivity.
Step 3: Check Collector Status
Navigate to Auvik Collectors and review the collector status.
Look for indicators such as:
- Not Connected
- Not Approved
- Offline
- Upgrade in Progress
Step 4: Review Recent Changes
Determine whether any recent changes occurred, including:
- Firewall modifications
- Proxy deployments
- DNS changes
- Hypervisor maintenance
- Operating system updates
- Network security changes
Step 5: Confirm Cloud Connectivity Requirements
Verify that the collector can communicate with the required Auvik cloud services and that outbound HTTPS traffic is permitted.
Multi-Collector Environments
In environments with multiple collectors, this alert may not result in a complete loss of monitoring.
Depending on your deployment:
- Another collector may automatically assume monitoring responsibilities.
- Monitoring may continue for some networks while others become unavailable.
- TrafficInsights, Syslog, or other collector-specific services may still be affected.
Review collector assignments to determine whether monitoring redundancy is available.
Additional Information
If the collector reconnects successfully, monitoring and discovery resume automatically. No manual rescan is typically required.
If the collector remains disconnected after completing the troubleshooting steps above, see Troubleshooting the Auvik Collector or contact Auvik Support for assistance.