Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/IT Service Level Management Description, User's Guide, Reference and Operator's Guide


10.2.3 Caution service area

Organization of this subsection

(1) Window configuration

[Figure]

(2) Window description

This window displays a ranked list of the monitored services based on the number of errors or warnings that occurred in each service during the last seven days. The display is updated every three seconds. The order in which the monitored services are listed is determined as follows:

  1. The monitored service with the most errors appears first and the monitored service with the fewest errors appears last.

  2. When the number of errors is the same, the monitored service with the most warnings appears first.

  3. When the number of warnings is the same, the monitored services and service groups appear according to the Unicode ordering of their names.

The following table lists the items that are displayed:

No.

Item

Description

1

Service

This column displays the names of the monitored services that the logged-in user is responsible for monitoring.

2

Service group

This column displays for each monitored service the name of the service group to which it belongs.

3

Current

This column displays each monitored service's current composite monitoring result for average response time, throughput, and error rate, using the following icons:

[Figure] (error)

There is at least one item for which an error has occurred in threshold monitoring.

[Figure] (warning)

There is at least one item for which a warning has occurred in trend monitoring or out-of-range value detection.

[Figure] (normal)

The status of all items is normal.

[Figure] (monitoring stopped)#

The monitored service is not currently being monitored.

If monitored targets within a monitored service have different statuses, the highest-priority status icon is displayed, according to the following priority order (highest to lowest): error > warning > normal. (In the case where monitoring of a monitored service has stopped, only the stopped status is possible.)

Consider an example with the following three statuses:

  • All Web Access: [Figure] (normal)

  • Web transaction 1: [Figure] (normal)

  • Web transaction 2: [Figure] (warning)

In this case, the status of the monitored service would be [Figure] (warning).

4

Error, Warning

These columns display for each monitored service the cumulative numbers of errors and warnings during the past seven days.

#

A monitored service will also be shown in the Current column as stopped if the process executing performance analysis of a monitored target within that monitored service experiences a memory shortage or abnormal termination of a thread after monitoring starts. In this case, stop the monitoring of the corresponding monitored service, and then restart monitoring after you have addressed the cause based on the KNAS32021-E message in the message log.

For details about the message log, see 7.2.3 Message logs.

(3) Supplemental notes