Creating Complex Alerts in SolarWinds

Monalytic walks you through creating a complex alert that will not trigger until a defined number of nodes have matched the trigger condition that was created. This alert will be created to fire when more than three virtual machines have media (i.e. CD_ROM) connected. Connected media can prevent vMotion from processing correctly.

  • Prerequisites
  • Creating a Complex Alert
  • Best Practices and Areas to Watch Out For


  • Create a custom property containing the nodes to be alerted on.

Creating a Complex Alert 

  1. Log into the SolarWinds Web Console with an account that has at least alert privileges.
  2. Click Settings → All Settings → Manage Alerts → Add New Alert
  3. Name the alert, add a description and make sure the alert is enabled. You can also set the severity of the alert. Click next and move to the Trigger Condition tab.
  4. Under the Trigger Condition tab, set the conditions that the alert will fire on. Once, the alert is configured, check the box to Enable complex conditions. Here you set the number of objects that have met the condition and the length of time the condition must exist for the alert to fire. Click next and move to the Reset Condition tab.
  5. Under the Reset Condition tab, set the threshold for when the trigger condition no longer exists. Click next and move to the Time of Day tab.
  6. Under the Time of Day tab, specify a schedule for the alert or specify that the alert is always enabled. Click next and move to the Trigger Actions tab.
  7. Under the Trigger Action tab, specify the message that is displayed when the rule fires and also what happens when the rule fires. Click next and move to the Reset Actions tab.
  8. Under the Reset Action tab, specify the action that is taken when the reset condition of the alert is met. Click next and move to the Summary tab.
  9. Under the Summary tab, review the configuration of the alert. If the alert is not configured correctly, you may edit it here. If it is correct, click Submit at the bottom of the screen.
  10. If the alert has been configured properly, and conditions are met to fire the alert, the alert will show up as an active alert.

Best Practices and Areas to Watch Out For

  • Use out-of-the-box alerts as templates. Find an alert that is similar to one you want to create and then click Duplicate & Edit in the menu bar.
  • Scope alerts based on who needs to see the alert.
  • Create alerts that are meaningful and will not just generate noise.
  • Create dependencies. Dependencies will prevent you from getting duplicate alerts based on a single network event. For example, your network has a router with switches behind it. Create a dependency with the router being the parent and the switches the children. Now if the router goes down, you will only get an alert on the router and not the switches.

If you’ve invested in SolarWinds or other monitoring or analytics software, but don’t have the time or staff to extract and analyze the information you need, we’re here to help. Let’s talk! Monalytic is an authorized SolarWinds partner specializing in project-based services, managed services, training, licensing, and maintenance renewals.

Back to News