Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

There are a series of settings that can be configured for each rule. Different configuration options are available for different types of rules.

  • For all rules you can configure the actions taken when a rule violation occurs. This includes specifying whether or not notifications will be sent out and whether or not the state of the object will change.
  • For most rules you can specify whether Events generated by the rule are “Error” Events or “Warning” Events. For “Warning” Events you can specify the “Event Count Escalation” (which determines the number of Events that cause the rule to escalate to an “Error” Event), and also the “Escalation/De-escalation Window” (which determines the time window that is considered for escalating and de-escalating the status of the Event).
  • For rules that relate to thresholds, you can specify the thresholds for logging “Warning” Events and “Error” Events. The rule defines the condition for escalating to a "Warning" and "Error" state and also the condition to de-escalate from "Error" state to "Warning" state and to "OK" state. The conditions are based on the percentage of the time that the object spent on a determined escalation/de-escalation timing window. Warnings and Errors use separate escalation and de-escalation windows, allowing users to better refine the escalation. For example, a source reporting blank picture for 5% of 60 minutes as a whole might constitute a
    warning.  But a source reporting blank picture for 10% of a 15 minute window, can be configured to escalate to an error.

The following is an example of the settings that can be configured for a rule that involves warning and error thresholds.

  • No labels