Downtime Behavior

Administration > Event Processing > Automation > Downtime Behavior

Alternatively, click Downtime Behavior.

A downtime configuration for a CI or a group of CIs primarily specifies the downtime period and the behavior (Action) for these CIs during this downtime period. If any other action is selected, for example Suppress events, the downtime behavior configured in OMi is applied.

For a CI with configured downtime periods, you must consider how to manage events that are related to this CI while it is unavailable. A category is assigned to the downtime configuration for a CI. Downtime strategies for event management are configured using Downtime Categories, which define how events related to a CI are handled when received while that CI was in downtime. By default, events for which the related CI is in downtime are closed automatically.

For example, a category may specify that:

• Lifecycle of the event is set to resolved

• Steps in the event pipeline are enabled or disabled

In this example, for all CIs that are associated with this category, events received during downtime are set to Resolved and are visible in the Event Browser. All events that are related to these events are automatically set to Closed and can be viewed from within the History Browser.

OMi provides a predefined list of categories and you can create additional categories using the Infrastructure Settings. Categories are selected and modified using the Categories list in the Downtime Management manager.

Downtime configurations that do not have a corresponding configuration in the OMi Downtime Manager use the category Default. (The Default category cannot be deleted.)

When a downtime period for a CI starts or ends, an event can be sent to the Event Browser indicating the start or end of this downtime period. An event that reports the end of a downtime period also closes the downtime-start event and is itself also immediately closed.

These downtime-start events can be forwarded to external servers such as trouble ticket systems using event forwarding rules. When the downtime-end event is received, the change of state of the downtime-start event is then also forwarded to the trouble ticket system.

The Automatically forward "downtime started" events to Trouble Ticket System event forwarding rule can be activated and used to automatically forward events indicating the start of a CI downtime to the Trouble Ticket System. This system must be configured in the alias connected server called "Trouble Ticket System". Use this rule if you do not have an alternative rule to forward the downtime-start events. Downtime-end events automatically closed the downtime-start events. For further details, see Event Forwarding.

For details about configuring downtime, see Downtime Management.

The following infrastructure settings relate to downtime behavior:

• Downtime History Range — Time period within which past downtime configurations are considered. All downtime periods which have an end time that is before the beginning of the configured downtime history range period are ignored. Events created during such downtimes are treated as events not created during a downtime.

• Future Downtime Range — Time period within which future downtime configurations are considered. All downtime periods which have a start time that is after the end of the configured future downtime range period are ignored. Events created during such downtimes are treated as events not created during a downtime.

• Refresh Time Interval — Maximum time after changes in the maintenance windows configuration are taking effect.

1. In the Categories pane, click the  New Item button to open the Add New Downtime Category dialog box.

2. Select a category from the Category Name list.

   A category is associated with each downtime configuration. When an event is received from a CI while in downtime, depending on the category of the CI downtime configuration, the appropriate downtime category is applied. If no suitable downtime category is available, the Default downtime category is applied.

3. In the Set Lifecycle State section, select an action from the following choices:

   • No change — retains the original state of the event

   • Closed — changes the state to Closed for events that are related to CIs which are in downtime of the specified category (default)

   • Resolved — changes the state to Resolved for events that are related to CIs which are in downtime of the specified category

4. In the Active Pipeline Steps section, select the pipeline step that you want active for this downtime category:

   • EPI after CI/ETI Resolution — Apply event processing after the CI and ETI resolution steps

   • Close Related Events — Close all events related to the event received during downtime of CI

   • Duplicate Event Suppression — Apply the Duplicate Event Suppression settings to events received during downtime of CI

   • Automatic User Group Assignment of Events — Apply the automatic assignment of user or group to events received during downtime of the CI

   • EPI before Storing Events — Apply event processing at the end of the event processing stage

   • Topology-Based Event Correlation — Apply Topology Based Correlation Rules to events received during downtime of the CI

   • Automatic Run Books — Apply Run Book Automation to events received during downtime of CI

5. Select Show Confirmation Dialog, if you want a confirmation dialog box to be displayed before launching tools and actions.