Auvik includes a library of pre-configured alerts designed to help identify availability, performance, configuration, and monitoring issues across your network.
Most pre-configured alerts can be edited, disabled, reset, or deleted. You can also create custom alerts to meet your organization's monitoring requirements.
You can filter the alert list to display specific alerts. For more information, see How to filter data in Auvik.
Alert Scope and Inheritance
Alerts can be managed at either the top level (MSP) level or the site level.
Top Level (MSP) Dashboard
Alerts created or modified from the MSP dashboard are applied across all managed client sites.
Site Dashboard
Alerts created or modified from a site dashboard affect only that specific site.
Note: Changes made to an alert at the site level are not overwritten by future changes made to the same alert from the MSP dashboard.
Alert Types
Auvik supports alerts for:
- Network, device, and interface monitoring
- Service monitoring
- VMware component monitoring
- Collector monitoring
- SNMP pollers and custom metrics
- Hardware and lifecycle monitoring
Alerts can be applied broadly across all entities or targeted to specific devices, services, interfaces, or components.
Create an Alert
Alerts v2
For sites using Alerts v2:
- Navigate to Manage Alerts.
- Click Create New Alert.
- Search for the metric or trigger you want to monitor.
- Select the desired trigger.
- Click Next Step.
- Configure:
- Alert name
- Description
- Severity
- Trigger condition
- Clear condition
- Notification settings
- Click Save.
Note: If an Alerts v2 trigger exists, Auvik creates an Alerts v2 alert by default.
For SNMP pollers, search for the poller name when selecting a metric.
Alerts v1
For sites using the legacy alert framework:
- Navigate to Manage Alerts.
- Click Add Alert.
- Select the alert type:
- Network/Device/Interface
- Service
- Component
- Collector
- Complete the alert configuration form.
- Click Save.
Configure Alert Conditions
Every alert requires:
- Alert name
- Description
- Severity
- Trigger condition
- Clear condition
Clear Condition Options
Inverse of Trigger Condition (Default)
Automatically clears the alert when the trigger condition is no longer true.
Example:
- Trigger: Device Status = Offline
- Clear: Device Status = Online
No Clear Condition (Clear by Dismissing)
The alert remains open until manually dismissed.
This option is commonly used for workflow-driven alerts that require manual review.
Custom Clear Condition
Allows you to define a separate condition that clears the alert.
Example:
- Trigger: Collector Offline Duration ≥ 2 Minutes
- Clear: Collector Status = Online
Configure Notifications
Alerts can be associated with one or more notification channels.
Notification channels may include:
- PSA integrations
- Microsoft Teams
- Slack
- Webhooks
- Other configured integrations
You can also choose not to associate a notification channel.
Note: Alerts without notification channels still appear in the Alerts dashboard and remain available for auditing and reporting.
Configure Alert Pausing
To reduce alert fatigue, Auvik can automatically pause repeated alerts generated against the same entity.
When configuring an alert:
- Enable or disable automatic pausing.
- Configure pause duration.
- Configure repetition thresholds.
Automatic pausing helps prevent large numbers of duplicate alerts during ongoing outages.
Edit an Alert
To edit a single alert:
- Navigate to Manage Alerts.
- Select the alert.
- Click Edit.
- Make the desired changes.
- Click Save.
Depending on the alert type, some trigger and clear conditions may be locked to prevent invalid alert logic.
Note: Editing an alert from the MSP dashboard affects all client sites that inherit that alert.
Bulk Edit Alert Pause Settings
You can edit pause settings for multiple alerts simultaneously.
- Navigate to Manage Alerts.
- Select the alerts you want to modify.
- Click Edit.
- Choose:
- Automatically Pause Repeated Alerts
- Pause Length
- Apply the desired settings.
- Click Save.
Important: Pause Length can only be modified when all selected alerts have the same severity.
Reset Alerts
Resetting restores an alert to its inherited or default configuration.
You can reset:
- Auvik pre-configured alerts
- MSP-level alerts
You cannot reset:
- Site-specific custom alerts
To reset an alert:
- Navigate to Manage Alerts.
- Select the modified alert.
- Click Reset.
- Confirm the action.
Note: Resetting an alert does not modify its associated notification channels.
Delete Alerts
To permanently remove an alert:
- Navigate to Manage Alerts.
- Select the alert.
- Click Delete.
- Confirm the action.
Warning: Deleting an MSP-level alert removes it from all client sites.
Restore Deleted Alerts
Deleted Auvik alerts and MSP-shared alerts can be restored.
To restore an alert:
- Navigate to Manage Alerts.
- Click the settings menu.
- Select Restore Alerts.
- Choose the alerts to restore.
- Click Restore.
You cannot restore site-specific alerts that were created directly on an individual client site.
Disable Alerts
Disabling an alert prevents it from generating future alert events.
- Navigate to Manage Alerts.
- Select the alert.
- Click Disable.
- Confirm the action.
The alert remains configured but is no longer evaluated.
Tip: Disable an alert if you do not want it to trigger. If you only want to stop notifications, remove the notification channel instead.
Enable Alerts
To re-enable a disabled alert:
- Navigate to Manage Alerts.
- Select the alert.
- Click Enable.
- Confirm the action.
The alert immediately resumes normal evaluation.
Turn Off Notifications
If you want alerts to continue being generated without sending notifications:
- Navigate to Manage Alerts.
- Edit the alert.
- In the notification section, select No Notification.
- Save the alert.
Alternatively, remove all associated notification channels.
When notifications are disabled:
- Alerts continue to be generated.
- Alerts continue to appear in the Alerts dashboard.
- Historical alert data remains available.
- No emails, banners, or integration notifications are sent.
Best Practices
- Create alerts at the MSP level whenever possible to maintain consistency.
- Use site-level overrides only when a client requires unique monitoring thresholds.
- Configure pause conditions to reduce alert storms.
- Regularly review disabled alerts to ensure important monitoring is not being missed.
- Prefer Alerts v2 definitions when available, as they provide greater flexibility and support for newer monitoring features.
- Avoid creating duplicate alerts that monitor the same condition.
Proper alert configuration helps reduce noise while ensuring important operational issues are identified and escalated appropriately.