Let us learn about the event policy constructs and action
Event policies allow you to specify one or more rules
and group the rules into a policy set. The policy allows to configure
a maximum of 16 policy sets at
the site level but only one policy set can be active per site at
a given time. Each policy set can have a maximum of 128 policy rules.
The policy rules are explicitly ordered in a policy set.
A policy rule supports the following constructs and action attributes:
Resource Type—This indicates the resource on which the event
policy rule is be applied. The supported resource types are Application
Definitions, BGP Peers
Sub-Resource Types—Some of the resource
types have sub-resource types. You can specify a sub-resource type
to narrow down the match criteria to more specific elements. When
no sub-resources are specified, the policy applies the rule to all
the available sub-resources. For example, when you select the resource
type as Circuits, you can select one of the available sub-resource
type as Public or Private.
Event Codes—Matched event codes indicate the system generated
alarms on which the event policy rule must act upon.
Schedule—Specify a schedule indicating the
start and end date in MM/DD/YYYY HH: mm format. When no schedule
is applied, the event policy rule is applied immediately.
Suppress—This indicates whether the event policy rule suppresses
or unsuppress the alarms on the resources identified by the resource
type, sub-resource type, or matched event codes during the specified
Priority—This indicates a user defined priority level that overrides
the default priority assignment for system generated alarms.
Escalation Rules—Matched alarms can have their priority escalated
based on the following scenarios:
Standing Rule—If an alarm
has been standing for more than the specified period, then the alarm's
priority can be escalated.
Flap Rule—If the selected resource flaps more than the rate
specified during the defined interval, then a new flap rate exceeded
alarm will be generated.