Setting Alerts v2 Trigger Conditions

Auvik Alerts v2 trigger conditions let you define exactly what needs to happen on your network before an alert is raised—giving you more control and cutting down on noise. With flexible options like AND/OR logic, time-based thresholds, and detailed metric filters, you can create smarter, more specific alerts that reflect what’s really going on. Whether you're keeping an eye on device uptime, interface status, or unusual traffic, trigger conditions help make sure you’re only alerted when it truly matters.

By using boolean AND/OR clauses, you can string together various conditions and define a timing element so the alert doesn’t necessarily trigger immediately.

Condition Builder

Use the condition builder to specify the parameters of the alert by utilizing AND/OR boolean statements and various properties of devices.

• Use + Add Rule to add a new rule to a boolean group. A rule is a device condition you want either to be true or false. For example, Memory Utilization >= 90 is a rule. All rules within a boolean AND/OR group are subjected to that boolean logic. E.g. two rules under a “All conditions must be true (AND)” group specify that both rules must result true for this alert to be successful.

• Use + Add Group to create a new boolean group. You can chain together multiple boolean clauses each containing different rules. This allows you to create rich boolean statements like (A AND (B OR C) AND NOT D).

• For alert type definitions of interfaces, Windows services, components, component sensors, functions, disk partitions and BGP neighbors on a device, you can trigger the alert:
  •  
    • When For any is selected, you can decide whether you want to receive a notification for every sub-item that meets the trigger conditions or group them into a single notification Roll-up Alerts: Send one notification for multiple items during active trigger
      • Disabled (default) - Receive a notification for every sub-item that meets the trigger conditions.
      • Enabled - Receive a single notification for multiple items that meet the trigger conditions during the active trigger.

• For advanced (mixed expressions), you can include device and interface conditions. You can add rules and groups to each condition block as described above to create an alert which looks for both device and interface conditions to be true.
  
  

Trigger Message

The Trigger Message is the summary of the alert you’ll see in notifications when an alert has first been triggered. It is independent of the Clear Message which is used when an alert clears. You can specify references to various properties of the device (such as the make and model of the device) to create dynamic messages to allow you to identify and troubleshoot quickly when seeing an alert’s notification.

How to define Global Clear Condition

The clear condition determines when a triggered alert is no longer an issue and the alert can be cleared.

Clear Condition

Similar to legacy alerts there are three options:

Default – Inverse of Trigger Condition

By default, the inverse condition is used to clear the alert.

No Clear Condition – Clear by Dismissing

This requires a user to explicitly clear the alert from the Auvik portal.

Note: This is a selectable option in the Beta, but a known issue prevents an alert from being closed when a user performs the clear action from the All Alerts page. This impacts the alert in the Auvik portal, the API and any integrations. This will be addressed by the GA release.

Custom Clear Condition

Users can build their own clear conditions similar to how the trigger conditions were built (Check out Creating Alerts > Trigger Conditions for more details).

Auto Clear

This option will automatically clear a triggered alert after a specified duration. This duration can be set in minutes or hours, with a minimum value of 1 minute. Auto clear eliminates the need for manually dismissing informational event notifications.

Clear Message

The Clear Message is the summary of the alert you’ll see in notifications when an alert has been cleared. It is independent of the Trigger Message which is used when an alert first triggers. You can specify references to various properties of the device (such as the make and model of the device) to create dynamic messages to give you the information you need quickly when seeing an alert’s notification.

For Alerts v2, we can only specify Collector, Device & VMware properties in the Clear Message. Interface, Service & other properties will be available in the Commercial Availability release.

For a list of all device and interface properties for Alerts v2, click here.