Incident Policy Constructs
Expand all | Collapse all
Incident Policy Constructs
Let us learn about the Incident policy constructs and action attributes.
Incident 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 incident policy rule is be
applied. The supported resource types are Application Definitions, BGP Peers
, Cellular Modules
, Circuits, Devices, Interfaces,
Path Policy Sets, QoS Policy Sets, Secure Fabric Links
,
Service Endpoints
, and Sites.
(Optional)
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.
Incident Codes—Matched incident codes indicate the system generated incidents on
which the incident policy rule must act upon.
(Optional)
Schedule—Specify a schedule indicating the start and end date in
MM/DD/YYYY HH: mm format. When no schedule is applied, the incident policy rule is
applied immediately.
Suppress—This indicates whether the incident policy rule suppresses or unsuppress
the incidents on the resources identified by the resource type, sub-resource type,
or matched incident codes during the specified schedule.
Priority—This indicates a user defined priority level that overrides the default
priority assignment for system generated incidents.
Escalation Rules—Matched incidents can have their priority escalated based on the
following scenarios:
Standing Rule—If an incident has been standing for more than the specified
period, then the incident'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 incident will be
generated.
