"Severe" Policy for CAPs Example

Previous Next JavaScript must be enabled to correctly display this content

"Severe" Policy for CAPs Example

This example policy generates alerts for CAPs that require attention.

Policy entity: CAPs

Policy severity: Severe – Alerts may be generated every hour.

Policy criteria: CAP Library Health is NOTOPERATIVE or CAP Library Health is DEGRADED.

Time/Events	Evaluation	Result
14:05:10 The policy is created and enabled. CAP 1A is in a DEGRADED state.	The policy is evaluated for all CAPs and matched for CAP 1A.	An alert is generated for CAP 1A and emails sent to the defined recipients.
15:01:12 CAP 2B goes into a NOTOPERATIVE state.	The policy is evaluated for all CAPs and matched for both CAP 1A and CAP 2B.	No new alert for CAP 1A. An alert is generated for CAP 2B and emails sent to the defined recipients.
15:05:20 CAP 1A is still DEGRADED and CAP 2B is still NOTOPERATIVE.	The policy is evaluated for all CAPs and matched for both CAP 1A and CAP 2B.	A new alert is generated for CAP 1A and emails sent to the defined recipients. No new alert for CAP 2B.
16:01:27 CAP 1A is still DEGRADED and CAP 2B is still NOTOPERATIVE.	The policy is evaluated for all CAPs and matched for both CAP 1A and CAP 2B.	No new alert for CAP 1A. An new alert is generated for CAP 2B and emails sent to the defined recipients.