Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Orion Platform > Orion Documentation > Orion Platform Administrator Guide > Use alerts to monitor your environment > How conditions are evaluated

How conditions are evaluated

Table of contents
No headers
Created by Caroline Juszczak, last modified by Magdalena.Markova on Dec 21, 2016

Views: 657 Votes: 1 Revisions: 6

This Orion Platform topic applies to the highlighted products:

DPAIMEOCETSIPAMLMNCMNPMNTASAMSRMUDTVMANVNQMWPM

Conditions are a set of user-defined rules governing alert triggers and resets.

All child conditions must be satisfied (AND)

Every child condition in the group must be true before the alert is triggered.

In the following example, there are three child conditions.

  • Node Status is equal to Up
  • Percent Loss is greater than or equal to 75
  • CPU Load is greater than or equal to 85

This alert will not trigger unless the Node is Up, packet loss is greater than or equal to 75%, and CPU load is greater than or equal to 85%.

You can also think of the condition as:

Alert when: (Node Status = Up) AND (Percent Loss >= 75) AND (CPU Load >= 85)

At least one child condition must be satisfied (OR)

At least one child condition must be true before the alert is triggered.

In this example the alert trigger reads:

Alert when: (Node Status = Up) OR (Percent Loss >= 75) OR (CPU Load >= 85)

In this situation, if any of the three conditions become true, the alert will trigger.

All child conditions must NOT be satisfied

Every child condition must be false before the alert is triggered.

In this example the alert trigger reads:

Do not alert when: (Node Status = Down) AND (Percent Loss <= 75) AND (CPU Load <= 85)

Alternatively, you can think of the trigger as:

Alert when: (Node Status != Down) AND (Percent Loss > 75) AND (CPU Load > 85)

The conditions have been inverted (Node Status = Down instead of Node Status = Up).

At least one child condition must NOT be satisfied

Any child condition must be false before the alert is triggered.

In this example the alert trigger reads:

Do not alert when: (Node Status = Down) OR (Percent Loss <= 75) OR (CPU Load <= 85)

Alternatively, you can think of the trigger as:

Alert when: (Node Status != Down) OR (Percent Loss > 75) OR (CPU Load > 85)

The conditions have been inverted (Node Status = Down instead of Node Status = Up).

 
Last modified

Tags

Classifications

Public