Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > User Device Tracker (UDT) > UDT Administrator Guide > Use Orion Platform advanced alerts > Set a trigger condition for an advanced alert

Set a trigger condition for an advanced alert

Table of contents
No headers
Created by Steven Bansil_ret, last modified by Steven Bansil_ret on Jan 27, 2017

Views: 66 Votes: 0 Revisions: 3

Properly defining alert trigger conditions to address specific network conditions on selected network objects can eliminate the need for alert suppression conditions. SolarWinds recommends the use of appropriately specific trigger conditions to define alerts instead of suppression conditions, if possible.

  1. Click Start > SolarWinds > Alerting, Reporting, and Mapping > Advanced Alert Manager.
  2. Click View > Configure Alerts.
  3. If you want to create a new alert, click New.
  4. If you want to copy or edit an existing alert, select an alert from the list, and then click Copy or Edit, as appropriate.
  5. Click Trigger Condition.
  6. Select the Type of Property to Monitor from the list.

    The following image is a screenshot from an Orion Network Performance Monitor installation. Other modules will look similar, but different objects may be present.


  7. If you select Custom SQL Alert, complete the following steps:

    1. Select the object on which you want to alert in the Set up your Trigger Query field.
    2. Provide your custom SQL in the field below the object selection query.
    3. If you want to delay the trigger of this alert, provide the value and unit of your desired alert trigger delay.
    4. If you want to confirm your provided SQL, click Validate SQL.
  8. If you select a type of monitored object, complete the following steps:
    1. Generate trigger conditions in the text field by selecting appropriate descriptors from the linked context menus and by clicking Browse (...) on the left of the text field.
    2. Click the linked text to select the number of conditions that you want to apply (all, any, none, not all). For more information about linked text conditions, see Understand condition groups.


    3. Click Browse (...) to view the following condition options:

      The has changed condition is only valid for the Last Boot, IOS Version, and IOS Image Family device characteristics.


      • To generate a condition based on a comparison of device states, click Add a Simple Condition.


      • To generate a condition based on a comparison of device fields and values, click Add a Complex Condition.
      • To define more conditions, click Add a Condition Group.
      • To remove a selected condition, click Delete Current Condition.
      • To change the order of your conditions, click Move Down or Move Up, as appropriate.
    4. If you need an additional condition, click Browse (...), and then click Add ConditionType, as appropriate for the condition you want to add.
    5. If you need to delete a condition, click Browse (...), next to the condition you want to delete, and then click Delete Current Condition.


      • Conditions may be exported for use with other alerts by clicking Export Conditions and save.
      • Click Import Conditions to import existing conditions from other alerts. Imported trigger conditions automatically overwrite any existing trigger conditions.
    6. If you want to specify a time duration for the condition to be valid, type the interval and select Seconds, Minutes, or Hours from the list.

      You may need to delay alert trigger actions until a condition has been sustained for a certain amount of time. For example, an alert based on CPU load would not trigger unless the CPU Load of a node has been over 80% for more than 10 minutes. To set up a sustained-state trigger condition, at the bottom of the Trigger Condition tab, provide an appropriate amount of time the alert engine should wait before any actions are performed. By default, the alert triggers immediately, if the trigger condition exists. The maximum alert action delay is eight hours after the trigger condition is met.

    7. If you are finished configuring your advanced alert, click OK.
Last modified
22:18, 26 Jan 2017