Hitachi

JP1 Version 12 JP1/Performance Management Planning and Configuration Guide


I.1 Records

Organization of this subsection

(1) Data model

The following table shows the data model versions for the health check agent that correspond to the PFM - Manager versions.

PFM - Manager version

Data model version

08-11

3.0

09-00

4.0

5.0

10-00

5.2

10-50 or later

5.4

The following table shows the records that support data model versions.

Record name (record ID)

Data model version

Description

3.0

4.0

5.0 or later

Health Check Detail(PD_HC)

Y

Y

Y

Detailed information of health check results

Host Availability(PI_HAVL)

--

Y

Y

Performance and running rate of each host

Host Detail(PD_HOST)

--

Y

Y

Details on the health check result for each host

Reserved Interval(PI)

Y

Y

Y

Reserved record

Reserved Detail(PD)

Y

Y

Y

Reserved record

System Overview(PI_SYS)

--

Y

Y

Operational status summary of hosts in the system

Legend:

Y: Supported

--: Unsupported

(2) Format of record explanations

The explanation of each record consists of the following items.

Function

Provides an overview of the performance data stored in the record and related notes.

Default values and values that can be changed

Shows in table format the default values for the performance data collection conditions that are set in the record and the values that can be changed by the user. The table below shows the items that are described for the default values, the values that can be changed, and their meanings. For details about each item shown in this table, see the chapter that explains management of operation monitoring data in the JP1/Performance Management User's Guide.

Table I‒1: Default values and values that can be changed

Item

Meaning

Changeable

Collection Interval

Performance data collection interval (seconds)

Yes: Can be changed.

No: Cannot be changed.

Collection Offset#1

Offset (in seconds) for starting performance data collection. For details about offsets, see the chapter that explains management of operation monitoring data in the JP1/Performance Management User's Guide.

For details about the performance data collection start time, see Chapter 3. Performance Management Functions.

Log

Whether to record collected performance data in the Store database.

Yes:

Record performance data. However, performance data will not be recorded if Collection Interval=0.

No:

Do not record performance data.

LOGIF

Condition to be used to determine whether to record collected performance data in the Store database

Sync Collection With#2

Whether to collect performance data that is to be synchronized with the records displayed in the value of the Description record property. For details, see the chapter that explains management of operation monitoring data in the JP1/Performance Management User's Guide.

Over 10 Sec Collection Time#3

Whether the collection of records takes 10 seconds or longer

Yes:

Sometimes takes 10 seconds or longer.

No:

Takes less than 10 seconds.

#1

A value between 0 and 32,767 seconds (within the value specified in Collection Interval) can be specified. When multiple data items are being collected, the system load will increase if they are all collected at the same time. Therefore, a collection offset is used to distribute the workload of the collection processing. Note that the data collection recording time is the same as that specified in Collection Interval regardless of the value specified in Collection Offset.

#2

When Sync Collection With is displayed, Collection Interval and Collection Offset are not displayed.

#3

This item appears when the collection of historical data takes precedence over the display of real-time reports. For details, see the chapter that describes troubleshooting in the JP1/Performance Management User's Guide.

ODBC key field

This field shows the primary key that you need in order to utilize the data of a record stored in the Store database in PFM - Manager or PFM - Base. Some ODBC key fields are common to all records, while others are unique to particular records. ODBC key fields unique to specific records are listed under this heading in each record's description. Only multi-instance records have unique ODBC key fields.

For the ODBC key fields common to all records, see I.1(3) List of ODBC key fields.

Lifetime

Lifetime is the period during which the integrity of the performance data collected in the record is guaranteed. For details about lifetime, see Chapter 3. Performance Management Functions.

Record size

Size of the performance data that is stored in the record during a single collection operation.

Fields

A table in which the record's fields are listed and described. The components of this table for each field are explained below.

PFM - View name (PFM - Manager name)
  • PFM - View name

    Field name (PFM - View name) displayed on PFM - Web Console.

  • PFM - Manager name

    Field name (PFM - Manager name) to be specified in the SQL when you want to use the SQL from PFM - Manager to utilize the data of the field stored in the Store database.

    In the SQL statement, the field name is described in a format that begins with the record's record ID. For example, in the case of the Interval (INTERVAL) field of the Host Machine Status (PD) record, the field name is specified as PD_INTERVAL.

Explanation

Explanation of the performance data that is stored in the field.

You can obtain any of the following as a field's performance data:

  • The average or percentage from the most recently collected data and the data collected during the previous intervals

  • Performance data only from the most recently collected data (including values accumulated internally by the OS)

  • Data from other fields (see Data source in the table of fields for each record)

Unless otherwise specified, the value obtained from a data collection interval is used.

Summary

The method (summary rule) used by Agent Store to summarize the data. For details about summary rules, see I.1(4) Summary rules.

Format

The data type, such as char and float, of the value in the field. For details about data types, see I.1(5) List of data types.

Delta

When data is collected as a cumulative value, a delta value is used to display the data as the amount of change in the value. For details about delta values, see I.1(6) Field values.

Data source

The calculation method for or the source of the field's value. For details about field values, see I.1(6) Field values.

(3) List of ODBC key fields

Some ODBC key fields are common to all records, while others are specific to individual records. This section lists the ODBC key fields common to all records. To utilize the data of a record stored in the Store database in PFM - Manager, you need the ODBC key fields.

For details about the ODBC key fields that are specific to each record, see the individual record descriptions.

Table I‒2: List of ODBC key fields common to all records

ODBC key field

ODBC format

Data

Explanation

record-ID_DATE

SQL_INTEGER

Internal

Record key that indicates the record's creation date

record-ID_DATETIME

SQL_INTEGER

Internal

Combination of record ID_DATE field and record ID_TIME field

record-ID_DEVICEID

SQL_VARCHAR

Internal

Name of the host on which the health check agent is running

record-ID_DRAWER_TYPE

SQL_VARCHAR

Internal

Category. The valid values are as follows:

m: Minute

H: Hour

D: Day

W: Week

M: Month

Y: Year

record-ID_PROD_INST

SQL_VARCHAR

Internal

Instance name of the health check agent

record-ID_PRODID

SQL_VARCHAR

Internal

Product ID of the health check agent

record-ID_RECORD_TYPE

SQL_VARCHAR

Internal

Record type identifier (4 bytes)

record-ID_TIME

SQL_INTEGER

Internal

Time at which the record was generated (Greenwich Mean Time)

(4) Summary rules

For records of the PI record type, data that is collected at the interval set in Collection Interval and data that is collected at specific intervals (minute, hour, day, week, month, or year) based on defined rules is stored in the Store database. The type of summary is defined for each field. This definition is called the summary rules.

Some summary rules require intermediate data to be retained during the summary period. In such a case, a field for retaining the intermediate data is added to the record in the Store database. This field is called an added field. Some added fields are displayed as record fields in PFM - Web Console. The added fields displayed in PFM - Web Console can be used as fields displayed in historical reports.

To distinguish from added fields that are added by summarization, the fields described in each record explanation in this section are called fixed fields.

The name of an added field is as follows:

The following table lists and describes the suffixes for the PFM - Manager name and for the corresponding PFM - View name, as well as the data that is stored in the field.

Table I‒3: List of suffixes for added fields

Suffix to PFM - Manager name

Suffix to PFM - View name

Stored data

_TOTAL

(Total)

Sum of the field values in the record over the summary period

_COUNT

--

Number of records collected during the summary period

_HI

(Max)

Maximum field value in the record during the summary period

_LO

(Min)

Minimum field value in the record during the summary period

Legend:

--: There is no added field.

Table I‒4: List of summary rules

Summary rule name

Description of summary rule

COPY

Stores the field value in the most recent record in the summary period.

AVG

Stores the average field value in the summary period.

The formula is as follows:

(Sum of field values) ÷ (number of collected records)

Added fields (Store database):
  • _TOTAL

  • _COUNT

Added field (PFM - Web Console):#
  • (Total)

ADD

Stores the sum of the field values over the summary period.

LO

Stores the minimum field value during the summary period.

HILO

Stores the maximum, minimum, and average field values during the summary period.

For a fixed field, the average value is stored.

The formula is as follows:

(Sum of field values) ÷ (number of collected records)

Added fields (Store database):
  • _HI

  • _LO

  • _TOTAL

  • _COUNT

Added field (PFM - Web Console):#
  • (Max)

  • (Min)

  • (Total)

--

Indicates that data is not summarized.

#

For fields whose PFM - Manager name contains PCT, the (Total) field added in PFM - Web Console cannot be used in historical reports.

(5) List of data types

The table below lists the data types for field values and their corresponding C and C++ data types. The values shown in the Field column under Data type are those shown in the Format column of the record field tables.

Table I‒5: List of data types

Data type

Size (bytes)

Description

Field

C and C++

char n

char()

n

Character data with a length of n bytes

float

float

4

Numeric value (3.4E ± 38 (7 digits))

long

long

4

Numeric value (-2,147,483,648 to 2,147,483,647)

short

short

2

Numeric value (-32,768 to 32,767)

string(n)

char[]

Value in parentheses

Character string with a length of n bytes. The last character is null.

time_t

unsigned long

4

Numeric value (0 to 4,294,967,295)

ulong

unsigned long

4

Numeric value (0 to 4,294,967,295)

(6) Field values

This subsection describes the values stored in the fields.

Data source

Each field contains a value that is obtained from Performance Management or a monitoring target program, or it contains a value that is derived from such a value by applying a formula. The source of each field's value or the calculation method used to obtain the field's value is indicated in the Data source column in the table of fields.

If a field's value was obtained by processing collected performance data, the character string in the Data source column of a health check agent indicates the calculation method used to obtain the field value. The following notation is used for the data source:

  • --: Indicates that the field's value was not obtained by processing collected performance data.

Delta

Data that indicates the amount a value has changed is called delta. For example, if the performance data value obtained during the first collection is 3 and the performance data value obtained during the second collection is 4, the value 1 is stored as the change amount. In the tables, the Delta column indicates whether each field's value is a delta value.

If Indicate delta value is selected in the real-time report settings, values are displayed from the first time data is collected. If a report requires initial data, 0 is displayed as the initial value and the value for collected data is displayed for the second and subsequent data collections.

The performance data collected by the health check agent varies as shown in the following table.

Table I‒6: Performance data collected by the health check agent

Record type

Delta

Data type

Indicate delta value#

Record value

PI record type

Yes

--

--

--

No

Real-time data

Selected

The displayed value is the actual value at the time of data collection.

Not selected

The displayed value is the actual value at the time of data collection.

• Historical data

• Alarm monitoring data

--

The displayed value is the actual value at the time of data collection.

PD record type

Yes

--

--

--

No

Real-time data

Selected

The displayed value is the actual value at the time of data collection.

Not selected

The displayed value is the actual value at the time of data collection.

• Historical data

• Alarm monitoring data

--

The displayed value is the actual value at the time of data collection.

Legend:

--: Not applicable

#

This column indicates whether one of the following items is selected in PFM - Web Console:

  • Indicate delta value in the report wizard's Edit > Indication settings(Realtime) window

  • Indicate delta value in Indication settings(Realtime) on the Properties page in the report window

The following notes apply to performance data collection:

The first performance data that is stored for a historical report on the health check agent is created from the data collected during the previous collection and the current collection. Therefore, it takes a maximum of twice as much time as the specified collection interval before the first performance data is collected since the collection of historical report data began.

Average and percentage values of fields

Some field average and percentage values are obtained as values per second based on the specified Interval of time and some are obtained as values per data collection interval. Unless otherwise specified, the average and percentage values indicate the values per data collection interval (when Interval is set to 60 seconds, data per-minute is obtained).

Value of the Interval field

The value of the Interval field depends on the record type, as shown below.

Table I‒7: Value of the Interval field

Record type

Instance type

Report type

Description

PI record type

Multi-instance record

Real-time report

The initial value is 0. The subsequent values are for the refresh interval# specified for the report (in seconds).

Historical report

Values for the refresh interval# specified for the report are displayed (in seconds).

If data is summarized, the last value collected is displayed.

Single-instance record

Real-time report

The initial value is 0.

The subsequent values are for the refresh interval# specified for the report (in seconds).

Historical report

Values for the refresh interval# specified for the report are displayed (in seconds).

If data is summarized, the total of the summarized record is displayed.

--

Multi-instance record

Real-time report

The initial value is 0.

The subsequent values are for the refresh interval# specified for the report (in seconds).

The value is always 0 for the following records:

  • Device Detail (PD_DEV)

  • Process Detail (PD)

  • Process End Detail (PD_PEND)

  • Service Process Detail (PD_SVC)

Historical report

Values for the refresh interval# specified for the report are displayed (in seconds).

The value is always 0 for the following records:

  • Device Detail (PD_DEV)

  • Process Detail (PD)

  • Process End Detail (PD_PEND)

  • Service Process Detail (PD_SVC)

Single-instance record

Real-time report

--

Historical report

--

Legend:

--: Not applicable

#

The refresh interval is obtained from the following formula:

Interval field value = Record Time field value - Record Time field value during the previous collection

(7) Fields that are added only when a record is recorded in the Store database

Table I‒8: Fields that are added only when a record is recorded in the Store database

PFM - View name

(PFM - Manager name)

Description

Format

Delta

Versions supported on

Data source

Agent Host

(DEVICEID)

Name of the host on which the health check agent is running

string (256)

No

All

--

Agent Instance

(PROD_INST)

Name of the host on which the health check agent is running

string (256)

No

All

--

Agent Type

(PRODID)

Product ID of the health check agent, expressed as a 1-byte identifier

char

No

All

--

Date

(DATE)

Record creation date (Greenwich Mean Time)#1, #2

char (3)

No

All

--

Date and Time

(DATETIME)

Combination of the Date (DATE) and Time (TIME) fields#2

char (6)

No

All

--

Drawer Type

(DRAWER_TYPE)

For a record of the PI record type, the data summarization type.

char

No

All

--

GMT Offset

(GMT_ADJUST)

Difference (in seconds) between Greenwich Mean Time and local time

long

No

All

--

Time

(TIME)

Record creation time (Greenwich Mean time)#1, #2

char (3)

No

All

--

Legend:

--: The field's value is not obtained by using the health check function to process performance data.

#1

A reference time during summarization is set because data is summarized for records of the PI record type.

Table I‒9: Setting for each record type

Type

Setting for each record type

Minute

0 second of the time when the record was created.

Hour

0 minute and 0 second of the time when the record was created.

Day

00:00:00 of the day when the record was created

Week

00:00:00 on Monday of the week when the record was created

Month

00:00:00 on the first of the month when the record was created

Year

00:00:00 on January 1st of the year when the record was created

#2

When data is displayed in reports, the Date field is displayed in the format YYYYMMDD, the Date and Time field is displayed in the format YYYYMMDD hh:mm:ss, and the Time field is displayed in the format hh:mm:ss.

(8) Fields that are output when data is exported from the Store database

The fields listed below are output when the jpctool db dump command is used to export data from the Store database. These fields are also added when data is recorded in the Store database, but they cannot be selected as fields to be displayed in reports because they are not displayed by PFM - Web Console. Do not use these fields for operations because they are used internally by the health check agent.

(9) Health Check Detail (PD_HC)

Function

This record stores the operating status data of PFM - Agent or PFM - RM, or the operating status data of hosts where PFM - Agent or PFM - RM operates. It is a multi-instance record. You can use this record to perform the following:

  • Configure alarms or actions that respond to changes in the operating status of agents.

    You can use integrated management products, such as JP1/IM, to monitor status changes made by the agent.

  • Confirm the monitoring result report in the service-level operating status monitoring mode.

    You can confirm detailed information collected in the service-level operating status monitoring mode, such as the status of agents and services that make up the agents, or the date and time when the status was updated.

Default values and changeable values

Item

Default value

Changeable

Log

No

Yes

Collection Interval#

300

Yes

Collection Offset

0

Yes

LOGIF

Blank

Yes

Over 10 Sec Collection Time

No

No

#

The value specified here is used as the pooling cycle for the health check function.

ODBC key field

PD_HC_AGENT

Lifetime

From the first time the agent was started until unsetup or uninstallation.

Record size
  • Fixed part: 716 bytes

  • Variable part: 1,023 bytes

Fields
Legend:

--: Not applicable

Common fields

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Record Type

(INPUT_RECORD_TYPE)

The name of the record. The value of this field is always HC.

--

char 8

No

--

Record Time

(RECORD_TIME)

The time when the record was created.

--

time_t

No

--

Interval

(INTERVAL)

The collection interval of the record (in seconds).

--

ulong

No

--

Monitoring Level by Num

(MONITORING_LEVEL_NUM)

The monitoring level of the health check function (numerical value). This is a reserved field and cannot be used.

--

short

No

--

Monitoring Level

(MONITORING_LEVEL)

The monitoring level of the health check function (character string) as one of the following values:

  • Host: Host-level operation status monitoring

  • Service: Service-level operation status monitoring

--

string (33)

No

--

Fields for determining the agent operating status

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Agent

(AGENT)

The service ID of the monitored agent.

--

string (259)

No

--

Host

(HOST)

The host where the monitored agent is running.

--

string (256)

No

--

Agent Category by Num

(AGENT_CATEGORY_NUM)

The type of the monitored agent (numerical value). This is a reserved field and cannot be used.

--

short

No

--

Agent Category

(AGENT_CATEGORY)

The type of the monitored agent (numerical value), as one of the following values:

  • Agent: PFM - Agent

  • Remote Monitor: PFM - RM

  • Remote Agent: Remote agent

--

string (33)

No

--

Polling Date and Time

(POLLING_DATETIME)

The date and time at which the monitored agent was polled.

--

time_t

No

--

Agent Op Status by Num

(AGENT_STATE_NUM)

The status of the monitored agent (numerical value), as one of the following#1:

  • 0: Not Supported

  • 4: Running

  • 8: Incomplete

  • 12: Stopped

  • 16: Unconfirmed

  • 24: Host Not Available

--

short

No

--

Agent Op Status

(AGENT_STATE)

The status of the monitored agent (character string), as one of the following#1:

  • Not Supported

  • Running

  • Incomplete

  • Stopped

  • Unconfirmed

  • Host Not Available

--

string (33)

No

--

Agent Op Status Change

(AGENT_STATE_CHANGE)

A flag indicating whether the status of the monitored agent has changed since the last time the agent was polled. This field can contain the following values:

  • 0: The status is unchanged

  • 1: The status has changed

--

short

No

--

Agent Op Status Cont-Count

(AGENT_STATE_CONT_COUNT)

Continuation count for the current Agent operation status (data model 5.2 or later)

--

short

No

#2

#1

The status displayed for the agent depends on the monitoring level of the health check agent. For details about the status, see the chapter that describes detecting problems within Performance Management in the JP1/Performance Management User's Guide.

#2

Number of times the same AGENT_STATE_NUM value occurred consecutively.

The initial value is 1 and the value is incremented up to 1440. Once 1440 is reached, the value remains at 1440 (value for count 1,441 is 1440).

Fields for determining the host operating status

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Host Op Status by Num

(HOST_STATE_NUM)

The status of the host where the monitored agent is running (numerical value). This is a reserved field and cannot be used.

--

short

No

--

Host Op Status

(HOST_STATE)

The status of the host where the monitored agent is running (character string), as one of the following:

For normal agents:

  • Success: Communication was successful

  • Failure: error-details: Communication failed. The details of the error are shown as follows:

    Remote Host Unavailable: The target host did not respond.

    Connection Unavailable: Connection could not be established with the target host.

    Socket Failure: Socket operation resulted in an error.

    Unknown: The status is unknown.

For remote agents:

  • Success: Communication with the host was successful

  • Failure: Communication with the host failed

  • Unknown: Unknown status

--

string (33)

No

--

Fields for determining the service operating status (Agent Collector and Remote Monitor Collector services)

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Collector Inclusion in Agent

(COLLECTOR_INCL_AGENT)

A flag indicating whether the status of the Agent Collector and Remote Monitor Collector services is considered when evaluating the agent status. 0 is set when the operating status of the host is monitored, and 1 is set when the operating status of the service is monitored.

  • 0: Not included

  • 1: Included

--

short

No

--

Collector Op Status by Num

(COLLECTOR_STATE_NUM)

Operating status of Agent Collector and Remote Monitor Collector services (numeric value). This is a reserved field and cannot be used.

--

short

No

--

Collector Op Status

(COLLECTOR_STATE)

Operating status of Agent Collector and Remote Monitor Collector services (string). The values are as follows:

  • Start Pending: The service is starting

  • Active: The service has started

  • Standalone Active: The service has started (in stand-alone mode)

  • Busy: The service is processing a request

  • Standalone Busy: The service is processing a request (in stand-alone mode)

  • Too Long Busy: The service is taking a long time to process a request#1

  • Standalone Too Long Busy: The service is taking a long time to process a request (in stand-alone mode)#1

  • Stop Pending: The service is stopping

  • Inactive: The service is stopped

  • Unknown: The status is unknown#2

--

string (33)

No

--

Collector Op Status Last-Updated

(COLLECTOR_STATE_LAST_UPDATE)

Date and time when the operating status of Agent Collector and Remote Monitor Collector services was updated

--

time_t

No

--

Collector Op Status Cont-Period

(COLLECTOR_STATE_CONT_PERIOD)

The duration of the operating status of the Agent Collector and Remote Monitor Collector services (in seconds).#3

--

time_t

No

--

Collector Op Status Change

(COLLECTOR_STATE_CHANGE)

A flag indicating whether the status of the Agent Collector and Remote Monitor Collector services has changed since the last time the agent was polled. This field can contain the following values:

  • 0: The status is unchanged

  • 1: The status has changed

--

short

No

--

#1

If Yes is specified for Busy as Inactive in the properties of the health check agent, this value is set when the service remains in Busy or Standalone Busy status for longer than the period of time specified as the Time to Busy as Inactive setting. In this case, the health check agent considers the service inactive when it determines the operating status of the agent.

#2

This value is set when performing host-level monitoring of operating statuses, or in the following cases when performing service-level monitoring of operating statuses:

  • When the service is not specified as a monitoring target.

  • When the host or the Status Server service on the host is stopped.

  • When the service does not support the status management function.

  • When the status management function is unable to confirm the status of the service for reasons such as the service having terminated abnormally, despite the service supporting the status management function. In this case, the health check agent considers the service inactive when it determines the operating status of the agent. You will need to restart the service to allow the service status to be recognized correctly.

#3

The duration of the operating status of a service is calculated from the difference between the time when polling took place (Polling Date and Time) and the time when the service entered the current operating status (Collector Op Status Last-Updated, Store Op Status Last-Updated, or AH Op Status Last-Updated). For this reason, make sure that the clocks are synchronized on all hosts that run Performance Management services.

Fields for determining the service operating status (Agent Store and Remote Monitor Store services)

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Store Inclusion in Agent

(STORE_INCL_AGENT)

A flag indicating whether the status of the Agent Store and Remote Monitor Store services is considered when evaluating the agent status. 0 is set when the operating status of the host is monitored, and 1 is set when the operating status of the service is monitored.

  • 0: Not included

  • 1: Included

--

short

No

--

Store Op Status by Num

(STORE_STATE_NUM)

Operating status of Agent Store and Remote Monitor Store services (numeric value). This is a reserved field and cannot be used.

--

short

No

--

Store Op Status

(STORE_STATE)

Operating status of Agent Store and Remote Monitor Store services (string). The values are as follows:

  • Start Pending: The service is starting

  • Active: The service has started

  • Standalone Active: The service has started (in stand-alone mode)

  • Busy: The service is processing a request

  • Standalone Too Long Busy: The service is processing a request (in stand-alone mode)

  • Too Long Busy: The service is taking a long time to process a request#1

  • Standalone Too Long Busy: The service is taking a long time to process a request (in stand-alone mode)#1

  • Stop Pending: The service is stopping

  • Inactive: The service is stopped

  • Unknown: The status is unknown#2

--

string (33)

No

--

Store Op Status Last-Updated

(STORE_STATE_LAST_UPDATE)

Date and time when the operating status of Agent Store and Remote Monitor Store services was updated

--

time_t

No

--

Store Op Status Cont-Period

(STORE_STATE_CONT_PERIOD)

The duration of the operating status of Agent Store and Remote Monitor Store services (in seconds)#3

--

time_t

No

--

Store Op Status Change

(STORE_STATE_CHANGE)

A flag indicating whether the status of the Agent Store and Remote Monitor Store services has changed since the last time the agent was polled. This field can contain the following values:

  • 0: The status is unchanged

  • 1: The status has changed

--

short

No

--

#1

If Yes is specified for Busy as Inactive in the properties of the health check agent, this value is set when the service remains in Busy or Standalone Busy status for longer than the period of time specified as the Time to Busy as Inactive setting. In this case, the health check agent considers the service inactive when it determines the operating status of the agent.

#2

This value is set when performing host-level monitoring of operating statuses, or in the following cases when performing service-level monitoring of operating statuses:

  • When the service is not specified as a monitoring target.

  • When the host or the Status Server service on the host is stopped.

  • When the service does not support the status management function.

  • When the status management function is unable to confirm the status of the service for reasons such as the service having terminated abnormally, despite the service supporting the status management function. In this case, the health check agent considers the service inactive when it determines the operating status of the agent. You will need to restart the service to allow the service status to be recognized correctly.

#3

The duration of the operating status of a service is calculated from the difference between the time when polling took place (Polling Date and Time) and the time when the service entered the current operating status (Collector Op Status Last-Updated, Store Op Status Last-Updated, or AH Op Status Last-Updated). For this reason, make sure that the clocks are synchronized on all hosts that run Performance Management services.

Fields for determining the service operating status (Action Handler service)

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

AH Inclusion in Agent

(AH_INCL_AGENT)

A flag indicating whether the status of the Action Handler service is considered when evaluating the agent status.

  • 0: Not included

  • 1: Included

--

short

No

--

AH Op Status by Num

(AH_STATE_NUM)

The operating status of the Action Handler service (numerical value). This is a reserved field and cannot be used.

--

short

No

--

AH Op Status

(AH_STATE)

The operating status of the Action Handler service (character string), as one of the following values:

  • Start Pending: The service is starting

  • Active: The service has started

  • Standalone Active: The service has started (in stand-alone mode)

  • Busy: The service is processing a request

  • Standalone Busy: The service is processing a request (in stand-alone mode)

  • Too Long Busy: The service is taking a long time to process a request#1

  • Standalone Too Long Busy: The service is taking a long time to process a request (in stand-alone mode)#1

  • Stop Pending: The service is stopping

  • Inactive: The service is - stopped

  • Unknown: The status is unknown#2

--

string (33)

No

--

AH Op Status Last-Updated

(AH_STATE_LAST_UPDATE)

The date and time when the operating status of the Action Handler service was last updated.

--

time_t

No

--

AH Op Status Cont-Period

(AH_STATE_CONT_PERIOD)

The duration of the operating status of the Action Handler service (in seconds).#3

--

time_t

No

--

AH Op Status Change

(AH_STATE_CHANGE)

A flag indicating whether the status of the Action Handler service has changed since the last time the agent was polled. This field can contain the following values:

  • 0: The status is unchanged

  • 1: The status has changed

--

short

No

--

#1

If Yes is specified for Busy as Inactive in the properties of the health check agent, this value is set when the service remains in Busy or Standalone Busy status for longer than the period of time specified as the Time to Busy as Inactive setting. In this case, the health check agent considers the service inactive when it determines the operating status of the agent.

#2

This value is set when performing host-level monitoring of operating statuses, or in the following cases when performing service-level monitoring of operating statuses:

  • When the service is not specified as a monitoring target.

  • When the host or the Status Server service on the host is stopped.

  • When the service does not support the status management function.

  • When the status management function is unable to confirm the status of the service for reasons such as the service having terminated abnormally, despite the service supporting the status management function. In this case, the health check agent considers the service inactive when it determines the operating status of the agent. You will need to restart the service to allow the service status to be recognized correctly.

#3

The duration of the operating status of a service is calculated from the difference between the time when polling took place (Polling Date and Time) and the time when the service entered the current operating status (Collector Op Status Last-Updated, Store Op Status Last-Updated, or AH Op Status Last-Updated). For this reason, make sure that the clocks are synchronized on all hosts that run Performance Management services.

Message text field

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Message Text

(MESSAGE_TEXT)

Detailed information about the operating status of the agent being monitored.

--

string (256)

No

--

Message text

Messages in the message text field are displayed as follows.

When performing host-level monitoring, or when service-level monitoring yields an agent status of Not Supported, Unconfirmed, or Host Not Available:

HC: HC_AGT

When service-level monitoring yields an agent status of Running, Incomplete, or Stopped:

HC: HC_AGT (Collector: HC_AC, Store: HC_AS [, Action Handler: HC_AH])

Legend:

HC_AGT: The operating status of the agent

HC_AC: The operating status of Agent Collector and Remote Monitor Collector services

HC_AS: The operating status of Agent Store and Remote Monitor Store services

HC_AH: The operating status of the Action Handler service

Example of message output

The following are examples of messages output to the Message Text field of a PD_HC record.

HC: Not Supported

HC: Running (Collector: Active, Store: Active)

HC: Incomplete (Collector: Active, Store: Inactive, Action Handler: Active)

HC: Stopped (Collector: Inactive, Store: Inactive)

HC: Host Not Available

(10) Host Availability (PI_HAVL)

Function

This record stores the performance and running rate data of hosts that make up the system. It is a multi-instance record. You can use this record to perform the following:

  • Confirm the running rate of hosts in a timescale.

    You can confirm the performance of each host.

Please note that for any host monitored only by a remote agent whose status is Unknown, the corresponding data for that host will not be stored.

Default values and changeable values

Item

Default value

Changeable

Log

No

Yes

Sync Collection With

Detail Records, HC

No

LOGIF

Blank

Yes

Over 10 Sec Collection Time

No

No

Common ODBC key field

PI_HAVL_HOST

Lifetime

From the first time the agent was started until unsetup or uninstallation

Record size
  • Fixed part: 681 bytes

  • Variable part: 292 bytes

Field
Legend:

--: Not applicable

Common fields

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Record Type

(INPUT_RECORD_TYPE)

The name of the record

COPY

char 8

No

--

Record Time

(RECORD_TIME)

The time when the record was created

COPY

time_t

No

--

Interval

(INTERVAL)

The collection interval of the record (in seconds)

COPY

ulong

No

--

Fixed field

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Host

(HOST)

Host name

COPY

string (256)

No

--

Availability

(AVAILABILITY)

Running rate (%)

(Running: 100%; Stopped: 0%)

AVG

float

No

--

Total Available Time

(TOTAL_AVAILABLE_TIME)

Running time (second)#

(Running: Interval; Stopped: 0)

ADD

ulong

No

--

Total Not Available Time

(TOTAL_NOTAVAILABLE_TIME)

Stopping time (second)#

(Running: 0; Stopped: Interval)

ADD

ulong

No

--

Total Monitoring Time

(TOTAL_MONITORING_TIME)

Monitoring time (second)#.

Always Interval.

ADD

ulong

No

--

Summary Start Date and Time

(SUMMARY_START_DATETIME)

The first storage time in the summary period.

Always Record Time when stored.

LO

time_t

No

--

Summary End Date and Time

(SUMMARY_END_DATETIME)

The final storage time in the summary period.

Always Record Time when stored.

COPY

time_t

No

--

#

Does not include the time when monitoring was suspended.

(11) Host Detail (PD_HOST)

Function

This record stores the information that summarizes the results for health check performed by hosts. It is a multi-instance record, and its key is the host name. You can use this record to perform the following:

  • Configure alarms and actions that respond to changes in the status of hosts.

    You can use integrated management products, such as JP1/IM, to monitor status changes made by the host.

Default values and changeable values

Item

Default value

Changeable

Log

No

Yes

Sync Collection With

Detail Records, HC

No

LOGIF

blank

Yes

Over 10 Sec Collection Time

No

No

Common ODBC key field

PD_HOST_HOST

Lifetime

From the first time the agent was started until unsetup or uninstallation

Record size
  • Fixed part: 716 bytes

  • Variable part: 325 bytes

Field
Legend:

--: Not applicable

Common fields

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Record Type

(INPUT_RECORD_TYPE)

The name of the record

--

char 8

No

--

Record Time

(RECORD_TIME)

The time when the record was created

--

time_t

No

--

Interval

(INTERVAL)

The collection interval of the record (in seconds)

--

ulong

No

--

Monitoring Level by Num

(MONITORING_LEVEL_NUM)

The monitoring level of the health check function (numerical value). This is a reserved field and cannot be used.

--

short

No

--

Monitoring Level

(MONITORING_LEVEL)

The monitoring level of the health check function (character string) as one of the following values:

  • Host: Host-level operation status monitoring

  • Service: Service-level operation status monitoring

--

string (33)

No

--

Fixed field

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Host

(HOST)

Host name

--

string (256)

No

--

Polling Date and Time

(POLLING_DATETIME)

Polling date and time

--

time_t

No

--

Status

(STATE)

Status

(Running: Available; Stopped: Not Available; Unconfirmed: Unknown)

--

string (33)

No

--

Status by Num

(STATE_NUM)

Status

(Running: 0; Stopped: 1; Unconfirmed: 2)

--

short

No

--

Status Change

(STATE_CHANGE)

Indicates whether there was a status change.

(No change: 0; Changed: 1)

--

short

No

--

Num of Agents

(NUM_AGENTS)

Total number of agents on the host

--

ulong

No

--

Num of Agents except Sus

(NUM_AGENTS_EXCEPT_SUS)

Total number of agents on the host (except for Suspended agents)

--

ulong

No

--

Num of Not Supported

(NUM_NOTSUPPORTED)

Number of Not Supported agents on the host#

--

ulong

No

--

Num of Running

(NUM_RUNNING)

Number of Running agents on the host#

--

ulong

No

--

Num of Incomplete

(NUM_INCOMPLETE)

Number of Incomplete agents on the host#

--

ulong

No

--

Num of Stopped

(NUM_STOPPED)

Number of Stopped agents on the host#

--

ulong

No

--

Num of Unconfirmed

(NUM_UNCONFIRMED)

Number of Unconfirmed agents on the host#

--

ulong

No

--

Num of Host Not Available

(NUM_HOSTNOTAVAILABLE)

Number of Host Not Available agents on the host#

--

ulong

No

--

Num of Suspended

(NUM_SUSPENDED)

Number of Suspended agents on the host (only the agents that are specified for suspension)#

--

ulong

No

--

#

For details about the operating status, see the chapter that describes detecting problems within Performance Management in the JP1/Performance Management User's Guide.

(12) Reserved Interval (PI)

This is a reserved record and cannot be used.

(13) Reserved Detail (PD)

This is a reserved record and cannot be used.

(14) System Overview (PI_SYS)

Function

This record stores select information, such as the number and availability of running hosts, as the operating status summary of the hosts that make up the system. It is a single-instance record. You can use this information to perform the following:

  • Use a snapshot to confirm the system's operating status summary.

    You can confirm the current system status, as well as the status history and trends.

Default values and changeable values

Item

Default value

Changeable

Log

No

Yes

Sync Collection With

Detail Records, HC

No

LOGIF

Blank

Yes

Over 10 Sec Collection Time

No

No

Common ODBC key field

None

Lifetime

From the first time the agent was started until unsetup or uninstallation.

Record size
  • Fixed part: 801 bytes

  • Variable part: 0 bytes

Field
Legend:

--: Not applicable

Common fields

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

Record Type

(INPUT_RECORD_TYPE)

The name of the record

--

char 8

No

--

Record Time

(RECORD_TIME)

The time when the record was created

--

time_t

No

--

Interval

(INTERVAL)

The collection interval of the record (in seconds)

--

ulong

No

--

Fixed field

PFM - View name

(PFM - Manager name)

Description

Summary

Format

Delta

Data source

% Available Hosts

(PCT_AVAILABLE_HOSTS)

Running rate of host (%)

HILO

float

No

#1

% Available Hosts except Sus

(PCT_AVAILABLE_HOSTS_EXCEPT_SUS)

Running rate of host (%) (except for suspended hosts)

HILO

float

No

#2

Num of Available Hosts

(NUM_AVAILABLE_HOSTS)

Number of running hosts

HILO

ulong

No

--

Num of Not Available Hosts

(NUM_NOTAVAILABLE_HOSTS)

Number of stopped hosts

HILO

ulong

No

--

Num of Unknown Hosts

(NUM_UNKNOWN_HOSTS)

Number of unconfirmed hosts

HILO

ulong

No

--

Num of Suspended Hosts

(NUM_SUSPENDED_HOSTS)

Number of suspended hosts (only the hosts that are specified for suspension)

HILO

ulong

No

--

Num of Hosts

(NUM_HOSTS)

Total number of hosts

HILO

ulong

No

--

Num of Hosts except Sus

(NUM_HOSTS_EXCEPT_SUS)

Total number of hosts (except for suspended hosts)

HILO

ulong

No

--

#1

NUM_AVAILABLE_HOSTS ÷ NUM_HOSTS × 100

#2

NUM_AVAILABLE_HOSTS ÷ NUM_HOSTS_EXCEPT_SUS × 100