Indicator Definitions

Administration > Service Health > Indicator Definitions

Alternatively, click Indicator Definitions.

This section provides a brief overview of ETIs and HIs. For more detailed conceptual information, see Service Health.

• ETIs. Multiple data collectors may send events regarding a single problem to OMi. The event subsystem generalizes these events into a common language by using ETIs. ETIs are categorizations of events according to the type of occurrence (for example, CPU load passing a threshold).

  Each CIT has various ETI definitions within the indicator repository that define which characteristics of a CI are of interest, and may be monitored by OMi.

  Indicator Mapping Rules within Operations Manager i map events to ETIs. For example, when the CPU load threshold is breached on your server, an event is sent to OMi. Based on the text strings in this event, it is assigned an ETI of CPU Load.

• HIs. HIs provide fine-grained measurements for the CIs that represent your monitored business elements and processes. HIs use event data to generate HI status.

When an event occurs in your monitored environment, a monitoring tool sends an event to the OMi event subsystem. Each event identifies the CI where the event occurred, and has a name and a state (for example, Event name = CPULoad; State = Overloaded).

When an event comes to OMi, it is associated with a CI. If the CIT of this CI does not have a corresponding ETI or HI definition, the event is considered informational, and no indicator is assigned.

If the CIT has a corresponding ETI or HI definition, and the event's state is one of the defined states, the event is assigned an ETI or an HI with a corresponding status.

Mapping events to ETIs and HIs

An event is mapped to an ETI or an HI as follows:

• ETI. An event can match an ETI definition either if a text string in the event has an explicit ETI field, or if Indicator Mapping Rules in OMi define that this event is mapped to a particular ETI.

  If an event matches an ETI definition but not an HI definition, the event is assigned an ETI, and it is displayed in the Event Browser. This has no impact on the CI's status in OMi.

• HIs. If an event's ETI also has a corresponding HI definition, an HI is assigned to the CI. If the HI already exists on the CI, its status is updated. The HI gets a state and status as defined in the HI definition.

This section provides an overview of how health indicators are calculated and how their relationships to CITs and ETIs work.

SiteScope monitor threshold status can have three possible severities: Error, Warning, and Good.

HIs can have many identifiers. For example, when measuring CPU Load, an HI's identifier might be Bottlenecked or Busy, whereas when measuring Memory Load, an HI's state might be Paging or Starving for Memory.

In addition, each HI can have one of the following severity levels: Critical, Major, Minor, Warning, Normal, and Unknown.

It is therefore necessary to map the severity of each SiteScope threshold status to its corresponding HI's state (identifier and severity). SiteScope monitors that have a defined topology and default mapping, also have an HI state that is assigned to the threshold status by default. Indicator states are assigned to the threshold status according to the closest available status that exists in the states, for the indicator associated with the threshold.

For example, when measuring percent used on a Memory monitor, the threshold is mapped to the Major status in the Error threshold because the Critical severity is not available for the Memory Load indicator. When measuring round trip time on a Ping monitor, the closest severity level in the Warning threshold is Major because the Minor severity level does not exist for this indicator state. The Good threshold is always mapped to the Normal severity level.

Indicator mapping for each monitor is defined within SiteScope in the HPE Integration Settings pane. For details, see SiteScope Help.

For HIs on SiteScope monitor CIs, status is based on the status received from SiteScope (calculated according to the thresholds defined in SiteScope). Three status levels are used in Service Health:

• OK (green) in Service Health corresponds to Good or OK status in SiteScope

• Minor (yellow) in Service Health corresponds to Warning status in SiteScope

• Critical (red) in Service Health corresponds to Error status in SiteScope

The SiteScope status definitions cannot be changed in Service Health, so the business rules for HIs on SiteScope monitors do not include threshold values.

The left area of the Indicator Definitions page contains a hierarchy of the CITs in your system. To view ETIs and HIs assigned to a CIT, you must select a CIT.

To view the details of an ETI or an HI, select it in the indicator's list and view its details in the right pane. The contents of this pane vary depending on the indicator's definitions. If you want to edit an existing indicator, click Edit.

If an ETI uses mapping rules, they are displayed in this section. You can edit mapping rules by clicking Edit Mapping Rules.

1. Select a CIT from the left pane.

2. In the central pane, click New to add a new indicator definition to the selected CIT. Alternatively, you can click New in the right pane.

   The Create Health Indicator panel opens.

3. In the General section, complete the following information:

   1. Enter a display name, an identifier (the internal name of the ETI or HI, as defined in the event generating the ETI or HI), and, optionally, a description of the ETI or HI.

      Important Each indicator in a subtree must have a unique name. For example, if you create an indicator on the Node CIT, you cannot use the same name for another indicator on the Computer CIT.

      Note The Identifier field is filled in automatically. For example, if you enter CPU Load as the display name, CPU_Load is automatically inserted in the Identifier field. Of course, you can specify another name in the Identifier field if you want to change it from the one suggested automatically. In this case, the identifier cannot contain blank spaces.

   2. Select the type of indicator you want to create, Health indicator with associated event type indicator (default) or Event type indicator.

4. Optional. In the States section, enter the following information:

   • For health indicator with associated event type indicator:

     Two states are automatically created (Normal and Critical). Click Edit to modify them as needed: enter a display name (the state of the HI as defined in the event, for example, Very high CPU) and an identifier for each of them, and then click Add states.

     Important Each HI must have at least two states defined. A state with the Normal status must be defined as the default state.

   • For event type indicator:

     One state is automatically created (Normal). Click Edit to modify it as needed: enter a display name (the state of the ETI as defined in the event, for example, Very high CPU) and an identifier, and then click Add states.

     Important Each ETI must have at least one state defined.

   Note You can create additional states by clicking New State. To change the severity corresponding to the indicator's state, select it from the Severity drop-down list.

   To edit or delete any state, click Edit or Delete.

5. Health indicator with associated event type indicator only:

   In the Format Value section, you can define the method for formatting the value of the HI (when relevant) by selecting the Format using the method check box, and then either by choosing a formatting method from the drop-down list of available methods, or specifying a method that you have defined and is not in the list of available methods. For details, see List of formatting methods.

   If you do not want to define the method for formatting the value of the HI, select the Do not format value check box.

6. Click Create.

After you create the indicator, it is assigned to the selected CIT (and to its child CITs). The indicator details appear in the right pane.

1. Select a CIT from the left pane to display its assigned indicators in the central pane.

   Tip You can see which CITs have indicators assigned (and how many) by checking the numbers next to them in the CI tree.

2. Select an HI or an ETI from the central pane, and click Edit. Alternatively, you can click Edit in the right pane where the indicator's details are displayed.

   The Edit Health Indicator or Edit Event Type Indicator panel opens.

   Tip ETIs and HIs have different icons. The following image shows an example of an ETI and of an HI:

   

3. Edit the selected indicator as required. For details on the information that you must provide in each section, see How to create an indicator definition.

4. Click Save.

1. Select a CIT from the left pane to display its assigned indicators in the central pane.

2. Select an ETI or an HI from the central pane, and click Edit. Alternatively, you can click Edit in the right pane.

   The Edit Health Indicator or Edit Event Type Indicator panel opens.

3. In the General section, select Health indicator with associated event type indicator instead of Event type indicator if you want to convert an ETI to an HI, or vice versa.
4. Edit the indicator as required.
5. Click Save.