Timeframes allow you to specify when the event management policy is active. For example, during scheduled database maintenance periods, you might want to activate an event suppression policy for maintenance-related events to reduce unnecessary event accumulation.
For events to be impacted by a timeframe setting, the timeframe must be active for the entire time that is specified in the policy.
Example
An escalation policy is defined to escalate an event to priority level 1 (escalated one level) after 10 minutes. Events are generated. No event is escalated for at least 10 minutes. Five minutes after the policy is enabled, the policy is disabled. Even though the policy was active at the beginning of the 10 minute period, no event is impacted by the policy because it is not active at the end of the 10 minutes.
An escalation policy is defined to escalate an event priority after 30 minutes with an active timeframe from 4:00 P.M. to 5:00 P.M. At 4:45 P.M. Events are generated. The active time period expires at 5:00 P.M. Events generated at 4:45 P.M. are not impacted by the policy because the timeframe is not active at 5:15 P.M.
The following table describes the types of timeframes you can use in an event management policy.
Timeframe types and descriptions
| | |
|---|
| | Local timeframes are used for event policies only. They are maintained in the cell and are only visible to a single cell.
You create local timeframes from the Event Management Policies tab of the administration console, as described in How-to-create-a-new-local-timeframe. |
