Predefined Content Guide › Business Logic Modules › Availability Management Business Logic Modules

Availability Management Business Logic Modules

The following sections describe the business logic modules used in the metrics common to availability and failure statistics.

Availability Management Assumptions

The following assumptions and basic behaviors are taken for all the modules under the Availability domain:

• The initial status of the Component, at the first calculation period, is Up, before any event is received to report on this component.
• There is a NONE status. When a resource status is unknown, the status up-to the NONE status is considered based upon the last resource real status.
• Whenever out of timeslot period is defined the exception period is handled in the same manner.
• In case the whole calculation period falls out of timeslot the result of the period is NULL.
• Forced Events: In some cases the information on the service availability from the monitoring tool is incorrect or not valid. For these cases, an additional event is defined that its status is forced over any event received prior to it. For example, if the Service was reported as Up and a Force Down event is received, the Service is considered as Down
• Incident Events: In some cases incident events reports for the availability status. For example "Incident – Open" for priority 1 ticket stands for DOWN status while "Incident – Resolved" for priority 1 ticket stands for UP status.
• When a new event arrives, the formula checks the status of the previous event. If the status of the previous event is down, the period between this event and the new one is considered as down.
• Events may be reported for the status of a specific component or device or globally for the service. In case both global and component events are reported, the global is considered as the real status.

Availability Management Event Types

The following Availability management event types provide the status for the availability of a specific device or service:

• Availability UP Event
• Availability DOWN Event
• Availability Force UP Event
• Availability Force DOWN Event
• Availability Force NONE Event

In addition to the above, incident events (as described in the Incident Management Module section) may be used to reflect the availability status of the service or of a device. For example Incident – Open may represent DOWN status while Incident – Resolved represents UP status.

Availability Event Type Structure

The following table shows the structure for all Availability event types: