"Warning" Policy for Drives Example

This example policy generates alerts for drives that require attention because they have ACTION or EVALUATE health.

Policy entity: Drives

Policy severity: Warning – alerts may be generated every 24 hours.

Policy criteria: Drive Health Indicator is ACTION, or Drive Health Indicator is EVALUATE.

Time/Events	Evaluation	Result
05:00:17, Day 1 The policy is created and enabled. Drive 1 health is EVALUATE. Drive 2 health is MONITOR.	The policy is evaluated for all drives and matched for Drive 1 but not Drive 2.	An alert is generated for Drive 1 and emails sent to the defined recipients. No alert for Drive 2.
08:12:24, Day 1 Drive 1 health goes to ACTION. Drive 2 health is still MONITOR.	The policy is evaluated for all drives and matched for Drive 1 but not Drive 2.	Since it has been less than 24 hours since the last alert for Drive 1, no new alert is generated. No alert for Drive 2.
13:37:01, Day 1 Drive 1 health is still ACTION. Drive 2 health goes to EVALUATE.	The policy is evaluated for all drives and matched for both Drive 1 and Drive 2.	No alert for Drive 1. An alert is generated for Drive 2 and emails sent to the defined recipients.
05:01:03, Day 2 Drive 1 health is still ACTION. Drive 2 health is still EVALUATE.	The policy is evaluated for all drives and matched for both Drive 1 and Drive 2.	Since it has been more than 24 hours since the previous alert for Drive 1, a new alert is generated and emails sent to the defined recipients. No new alert for Drive 2 since it has been less than 24 hours since the last alert for Drive 2.
17:08:43, Day 2 A new email recipient is added to the policy. Drive 1 health is still ACTION. Drive 2 health is still EVALUATE.	The policy is evaluated for all drives and matched for both Drive 1 and Drive 2.	No new alert for Drive 1. Since it has been more than 24 hours since the previous alert for Drive 2, a new alert is generated and emails sent to the defined recipients.

Time/Events

Evaluation

Result

05:00:17, Day 1

The policy is created and enabled.

Drive 1 health is EVALUATE.

Drive 2 health is MONITOR.

The policy is evaluated for all drives and matched for Drive 1 but not Drive 2.

An alert is generated for Drive 1 and emails sent to the defined recipients.

No alert for Drive 2.

08:12:24, Day 1

Drive 1 health goes to ACTION.

Drive 2 health is still MONITOR.

The policy is evaluated for all drives and matched for Drive 1 but not Drive 2.

Since it has been less than 24 hours since the last alert for Drive 1, no new alert is generated.

No alert for Drive 2.

13:37:01, Day 1

Drive 1 health is still ACTION.

Drive 2 health goes to EVALUATE.

The policy is evaluated for all drives and matched for both Drive 1 and Drive 2.

No alert for Drive 1.

An alert is generated for Drive 2 and emails sent to the defined recipients.

05:01:03, Day 2

Drive 1 health is still ACTION.

Drive 2 health is still EVALUATE.

The policy is evaluated for all drives and matched for both Drive 1 and Drive 2.

Since it has been more than 24 hours since the previous alert for Drive 1, a new alert is generated and emails sent to the defined recipients.

No new alert for Drive 2 since it has been less than 24 hours since the last alert for Drive 2.

17:08:43, Day 2

A new email recipient is added to the policy.

Drive 1 health is still ACTION.

Drive 2 health is still EVALUATE.

The policy is evaluated for all drives and matched for both Drive 1 and Drive 2.

No new alert for Drive 1.

Since it has been more than 24 hours since the previous alert for Drive 2, a new alert is generated and emails sent to the defined recipients.