Open topic with navigation

# Monitoring Rules

Monitoring rules are defined to generate monitoring warnings for each managed product type. ArcMC includes many preset monitoring rules for your use. You can use these rules as written, or customize them for your own use. In addition, you can create your own custom monitoring rules.

A monitoring rule comprises a set of logical, performance, health, or other criteria. All criteria in the rule are evaluated together to determine the rule’s total effect, which generates an alert from ArcMC.

Rules breaches will be displayed in the Warning Severity Issue Summary, which you can view by clicking one of the ring meters on the

Monitoring Dashboard.

For example, a rule could check for the number of input events per second (criterion #1) that reach a certain type of device (criterion #2). Should this number exceed (criterion #3) a specified level (criterion #4), then a warning (alert) should be returned.

Breach Function

The breach function checks the backend monitor metric data table. The metric data table is updated every 3 minutes, and the breach check function runs every four minutes at the 45th second. Reducing the rule's time range to a smaller number (e.g. 1 or 2) could result in an undetected breach.

Alerts can be delivered by email or by SNMP, or can be recorded in audit logs. Only when there is new breach detected (i.e. not found on the previous run), ArcMC sends the notification/alert if the notification option is enabled. If the breach keeps coming on the subsequent calls, the alert will only be sent the first time.

For more information on managing and creating rules, see Managing Rules .