Hitachi

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


4.5.1 Overview of report creation

ITSLM helps you create reports efficiently by displaying monitoring items to be checked as reports and saving reports as CSV files.

ITSLM enables you to achieve the following:

For details about the Report window, see 10.5 Report window and the windows displayed from the Report window.

Organization of this subsection

(1) Items that can be displayed in reports

ITSLM enables you to display in windows the following items as reports for purposes of verification (note that this information cannot be output to CSV files):

Service performance

Displays the service monitoring status of monitored services that are monitored in ITSLM. The items that can be displayed as service performance for monitored services include the monitored targets, monitoring items (units), average values, SLO compliance rates, and comparisons (as percentages) to previous periods.

This is the service performance of All Web Access or Web transactions under a selected monitored service.

System performance

When ITSLM is linked with Performance Management for monitoring of monitored services, displays the monitoring status of the hosts that are providing the monitored services. The items that can be displayed as system performance include the hosts, monitored targets, monitoring items (units), average values, SLO compliance rates, and comparisons (as percentages) to previous periods.

If a selected monitored service is not linked with Performance Management, this information is all blanks.

Availability information

When ITSLM is linked with Performance Management for monitoring of monitored services, displays service availability, MTTR, and MTBF as availability information.

If the monitored service is not running availability monitoring, the hyphen (-) is displayed as the value of service availability, MTTR, and MTBF.

Service availability overview

Displays the service start and stop times during the report period for the monitored services for which availability monitoring is running.

If availability monitoring is not running for a selected monitored service, this information is blanks. However, if availability monitoring is not running currently but was run at some point during the specified report interval, those availability monitoring results are displayed.

The following table provides the details of the items that can be displayed in reports.

Table 4‒3: Details of items that can be displayed in reports

No.

Item

Items in table

Value to be displayed

1

Service performance

Monitored target

Name of the selected monitored target

2

Monitor item (unit)

  • Average response time

  • Throughput

  • Error rate

3

Average#1

  • For average response time:

    Total average response time during the report interval / number of requests during the report interval (milliseconds)

  • For throughput:

    Number of requests during the report interval (excluding requests whose responses timed out before ITSLM - UR could receive them) / operation time during the report interval (count/second)

  • For error rate:

    (Number of times HTTP status returned an error response during the report interval + number of requests whose responses timed out before ITSLM - UR could receive them) / number of requests during the report interval (%)

4

SLO compliance rate#1

(1.0 - duration of overages of a threshold / operation time for one month) [Figure] 100 (%)

5

Comparison to a previous period (as a percentage)#2, #3

(Average response time during report interval / average response time during comparison period for the report interval - 1.0) [Figure] 100 (%)

6

System performance

Host

Host name of the selected monitored service

7

Monitored target

Name of the monitoring agent contained in the host

8

Monitor item (unit)

Name of a monitoring item contained in the monitoring agent

9

SLO compliance rate#1

(1.0 - duration of overages of a threshold / operation time for one month) [Figure] 100 (%)

10

Average#1

Average value for the monitoring item

11

Comparison to a previous period (as a percentage)#2, #3

(Average response time during report interval / average response time during comparison period for the report interval - 1.0) [Figure] 100) (%)

12

Availability info

Service availability %#2

(Sum of all operation periods during report interval / (sum of all operation periods during report interval + sum of all error periods during report interval) [Figure] 100) (%)

13

MTTR#1

Sum of all error periods during report interval / number of error periods during report interval (minutes)

14

MTBF#1

Sum of all operation periods during report interval / number of error periods during report interval (minutes)

15

Service availability overview

Date and time#4

Date and time an event related to availability monitoring occurred during the report interval

16

Event

One of the following events related to availability monitoring that occurred during the report interval:

  • Service stop

  • Service recovery

  • Start of service monitoring

  • Stop of service monitoring

#1

The value is rounded to the first decimal place.

#2

The value is rounded to the second decimal place.

#3

For a comparison to a previous period, the percentage is calculated for the monitored service's service performance or system performance, and the table header and the period used for comparison depend on the report interval setting.

The following table shows the relationship between the report interval and the previous period to which the percentage applies.

Table 4‒4: Relationship between report interval and previous period to which percentage applies

No.

Report interval

Table header

Period used for comparison

1

1 day

VS previous day

Day immediately preceding the start date

2

1 week

VS previous week

Seven days immediately preceding the start date

3

1 month

VS previous month

From the same date in the previous month to the preceding day

4

3 months

VS previous quarter

From the same date three months ago to the preceding day

#4

Displayed in the format YYYY/MM/DD hh:mm, based on the ITSLM - Manager's time zone.

(2) Performance charts displayed in reports

You can display performance charts in reports in addition to the monitoring items described in subsection (1). The displayed performance chart information can also be output to a CSV file.

A performance chart for a specified period (year or month) is displayed for each monitoring item. In the Preview report window, you can display a maximum of 10 monitoring items of your choice.

The axes and display range of each performance chart are as follows:

The following table describes the information that can be displayed in performance charts for the monitoring items.

Table 4‒5: Information displayed in performance charts

No.

Type of line graph

Information that is displayed

1

Maximum-value line

Line graph connecting the maximum measurement values.

2

Minimum-value line

Line graph connecting the minimum measurement values.

3

Average-value line

Line graph connecting the average measurement values.

4

SLO threshold value

Line graph connecting the monitoring item's threshold values.

Note: Measurement values obtained when the throughput is 0 are not used.

Plotting intervals of performance charts depend on the report interval settings.

The following table shows the relationship between the report interval and the performance chart's plotting interval.

Table 4‒6: Relationship between report interval and performance chart's plotting interval

No.

Report interval

Plotting interval of performance chart

1

1 day

Aggregate value for every 30 minutes

2

1 week

Aggregate value for two hours

3

1 month

Daily aggregate value

4

3 months

Daily aggregate value

Note that the plotting interval of a performance chart is the same as the interval of data output to a CSV file.

(3) CSV file format

ITSLM enables you to output the data for performance charts displayed in reports to CSV files. You can output a maximum of 50 monitoring items to a CSV file.

This subsection explains the CSV file name, output format, and output character encoding. It also presents output examples.

File names

The following table shows the file names that are displayed by default.

Table 4‒7: Default file names

No.

Report interval

File name

Interval in graph display

1

1 day

report_YYYYMMDD_d.csv

30 minutes

2

1 week

report_YYYYMMDD_w.csv

2 hours

3

1 month

report_YYYYMM_m.csv

1 day

4

3 months

report_YYYYMM_q.csv

1 day

Legend:

YYYYMMDD

YYYY, MM, and DD indicate the report start date selected in the Report window. You can change the file names.

Output format

The first line displays header information and the lines beginning with line 2 display data. The data is displayed in the same order as on performance charts displayed in the Report window.

  • Correspondence between header information and data

    The table below describes the correspondence between the header information that is output to the first line and the data that is output to the lines beginning with line 2.

    You can select the monitoring items to be output to a CSV file. If necessary, you can edit or add templates and set the monitoring items to be output to CSV files.

    Table 4‒8: Correspondence between the header information and the data beginning on line 2

    No.

    Monitoring item

    Header information#

    Data beginning on line 2

    1

    --

    Date

    Date and time ITSLM acquired the data

    2

    Average response time

    Average

    Average value of the average response times

    3

    Max

    Maximum value of the average response times

    4

    Min

    Minimum value of the average response times

    5

    Throughput

    Average

    Average throughput value

    6

    Max

    Maximum throughput value

    7

    Min

    Minimum throughput value

    8

    Error rate

    Average

    Average error rate value

    9

    Max

    Maximum error rate value

    10

    Min

    Minimum error rate value

    11

    Name of a monitoring item for a monitoring agent

    Average

    Monitoring item's average value

    12

    Max

    Monitoring item's maximum value

    13

    Min

    Monitoring item's minimum value

    Legend:

    --: Not applicable

    Note

    An average response time obtained when the average response time and throughput values are both 0 is treated as no data obtained, and is therefore not included in the average, maximum, and minimum values.

    Similarly, an error rate obtained when the error rate and throughput values are both 0 is treated as no data obtained, and is therefore not included in the average, maximum, and minimum values.

    #

    Under the header information output to a CSV file, the entries for Average, Max, and Min are displayed in this order for each monitoring item. The header information is displayed in the following format:

    monitored-target-name / monitoring-item-name

    For monitored-target-name and monitoring-item-name, the following information is displayed:

    monitored-target-name = All Web Access | Web-transaction-name | host-name / monitoring-agent-name

    monitoring-item-name = average-response-time | throughput | error-rate | name-of-monitoring-agent's-monitoring-item

  • Format of data

    The data that begins on line 2 is displayed in the following format:

    YYYY/MM/DD hh:mm,AA....AA

    YYYY/MM/DD hh:mm indicate the date (year/month/date) and time (hour:minute) the data was acquired by ITSLM.

    AA....AA indicates the comma-separated data items (values) acquired for each monitoring item. Average response time is in milliseconds.

Output character encoding

The character encoding used is UTF-8.

Output examples

Performance charts are output to a CSV file in the same order they are displayed in the Preview report window.

In the output example below, the monitored target is All Web Access and some of the data is omitted.

[Figure]

Note that in a report output for a month, if some of a day's data is missing for a reason such as the number of responses acquired by ITSLM - UR was zero, the header information is displayed, but no values are displayed.

Output example when some of a day's data is missing

[Figure]

If the aggregate data for a day is missing for a reason such as monitoring of the monitored target of the monitored service was stopped, the entire line for that day is omitted.

Output example when aggregate data for a day is omitted

[Figure]