N. Glossary

action

The operation that is automatically executed by Performance Management when the monitored data reaches the threshold. The following types of actions are available:

• E-mail transmission

• Command execution

• SNMP trap issuance

• JP1 event issuance

Action Handler

One of the PFM - Manager or PFM - Base services. It is a service for executing an action.

administration tool

Various types of commands and GUI functions that are used for checking service statuses and manipulating performance data. The following operations can be performed:

• Displaying service configuration and status

• Saving and restoring performance data

• Exporting of performance data to a text file

• Erasing of performance data

agent

The PFM - Agent service that collects performance data.

Agent Collector

One of the PFM - Agent services. It is a service for collecting performance data and evaluating performance data based on a threshold value that is set in an alarm.

Agent Store

One of the PFM - Agent services. It is a service for storing performance data. The Agent Store service uses a database for recording performance data. Each PFM - Agent has its own Agent Store service.

alarm

Information that defines the action to be taken or the event message to be issued when the monitored data reaches the threshold.

alarm table

A table into which one or more alarms are collected and which defines the following types of information:

• Objects to be monitored (Process, TCP, WebService, or the like)

• Information to be monitored (CPU usage, number of bytes received per second, or the like)

• Monitoring condition (threshold)

binding

The operation of associating an alarm with an agent. Once binding occurs, when the performance data collected by the agent reaches the threshold defined in the alarm, the user can be notified.

command registration file (espcommand.xml)

A file used to register created user-defined commands. This file is read when the Probe Daemon starts. Service-specific conditions for measuring a user-defined service are registered as command arguments in the command registration file.

Correlator

One of the PFM - Manager services. It is a service for controlling event delivery among services. When the alarm status being monitored by this service exceeds the threshold, this service sends an alarm event and an agent event to the Trap Generator service and PFM - Web Console.

database ID

An ID that is assigned to each record in PFM - Agent that indicates the database for storing records. A database ID indicates the type of records to be stored in the database. The following database IDs are used:

• PI: Indicates a database for records of the PI record type

• PD: Indicates a database for records of the PD record type

• PL: Indicates a database for records of the PL record type

data model

A general term for records and fields that each PFM - Agent has. Data models are managed according to version.

drilldown report

A report that is associated with a report or report field. You use a drilldown report to display the detailed information or related information of a report.

field

Individual operation information entries in a record. Each field serves as a monitoring item for Performance Management.

historical report

A report indicating the status of the monitoring target from the past to the present.

IE probe

A function for measurement (for measuring response performance of operations in Internet Explorer).

IE Probe Daemon

A service for measuring responses performance of operations in Internet Explorer.

IE probe management service

A service for managing the IE Probe Daemon.

IE Recorder

A GUI application used for defining IE scenario information and measurement conditions.

IE Recorder action condition definition file

A file defining IE Recorder's action condition settings. It is loaded when IE Recorder starts.

IE scenario

An operation or operations in the Internet Explorer defined as the measuring target of the response performance. You can define not only an operation but also multiple operations in the Internet Explorer as an IE scenario.

IE scenario file

A file used to define operation information in the Internet Explorer as an IE scenario when you measure IE scenarios. It is loaded when the IE Probe Daemon starts.

IE scenario measurement

You can measure the elapsed time between the time you perform operations in the Internet Explorer and the time these operations are completed as the response performance. You can monitor the approximate response performance to the ones users feel when operating in the Internet Explorer.

To measure an IE scenario, you create an IE scenario, define IE scenario information, and measure the response time of the Internet Explorer according to the IE scenario. Since not only an operation but also multiple operations in the Internet Explorer defined in the IE scenario are simulated to perform, you can measure the response performance of multiple operations as well as an operation in the Internet Explorer. You can measure the response performance of the any page transition as well as the response performance of the entire IE scenario. You can also detect problems of the measurement targets by checking the responses while measuring IE scenarios.

instance

In this manual, the term instance is used in the following ways:

• To indicate a recording format for records

  A record that is recorded in a single line is called a single-instance record; a record that is recorded in multiple lines is called a multi-instance record; and each line inside a record is called an instance.

• To indicate a PFM - Agent startup method

  When a single agent monitors the monitoring targets on the same host, it is called a single-instance agent. In contrast, when the monitoring targets support multiple instances, each agent can monitor each monitoring target instance. This is called a multi-instance agent. Each agent of a multi-instance agent is called an instance.

JP1/SLM

A product that performs monitoring from the viewpoint of performance as experienced by the service users of a business system, and that supports service-level maintenance. Linkage with JP1/SLM can enhance monitoring of the operating status.

lifetime

The duration in which the integrity of the performance data collected into each record can be guaranteed.

Master Manager

One of the PFM - Manager services. It is the main service of PFM - Manager.

Master Store

One of the PFM - Manager services. It is a service for managing the alarm events issued by each PFM - Agent. The Master Store service uses a database for holding event data.

measurement condition ID

A unique number assigned to a measurement condition for management purposes. A measurement condition ID cannot be duplicated because it becomes the identifier for each measurement condition. The same measurement condition can be registered more than once as separate measurement conditions, by assigning different measurement condition IDs.

measurement condition label definition file (esptasklabel.conf)

A file used to define a desired label name for the measurement conditions for each Internet service.

measurement condition registration file (esptask.xml)

A file used to register measurement conditions, such as the service type of the measurement target, the host name, and the measurement interval. This file is read when the Probe Daemon starts.

monitoring template

Predefined alarms and reports provided in PFM - Agent. The monitoring template enables you to easily prepare for monitoring the operating status of PFM - Agent without writing any complicated definitions.

multi-instance record

A record that is recorded in multiple lines. Such records have a specific ODBC key field.

See Instance.

Name Server

One of the PFM - Manager services. It is a service for managing the service configuration information inside a system.

ODBC key field

These fields display the primary keys that are necessary to use the data retrieved from records stored in the Store database on either PFM - Manager or PFM - Base. Some ODBC key fields are common to all records, while others are unique to some records.

password file

A file used to manage the passwords that are needed to log into Internet services. The password utility is used to register passwords into the password file. The registered passwords are converted to character strings.

password utility

The esppasswd command, which is used to register, change, and delete passwords.

PD record type

See Product Detail record type.

performance data

Resource usage data collected from a monitoring target system.

Performance Management

A general term for a group of software programs necessary for monitoring and analyzing issues related to system performance. Performance Management consists of the following five program products:

• PFM - Manager

• PFM - Web Console

• PFM - Base

• PFM - Agent

• PFM - RM

PFM - Agent

One of the program products comprising Performance Management. PFM - Agent that is equivalent to a system-monitoring facility. Various types of PFM - Agent are available according to the applications, databases, and OSs to be monitored. PFM - Agent has the following functions:

• Monitoring of the performance of the monitoring target

• Collection and recording of data from the monitoring target

PFM - Base

One of the program products comprising Performance Management. PFM - Base provides the basic functions for Performance Management to monitor operations. It is a prerequisite program product for PFM - Agent. PFM - Base provides the following functionality:

• Management tools such as various types of commands

• Common functions needed for linking Performance Management to other systems

PFM - Manager

One of the program products comprising Performance Management. PFM - Manager is equivalent to a manager facility and has the following functions:

• Management of Performance Management program products

• Management of events

PFM - Manager name

A name that identifies the field stored in the Store database. This name is used for specifying a field in a command.

PFM - View name

The alias of a PFM - Manager name. The PFM - View name is more intuitive than the PFM - Manager name. For example, the PFM - View name of the PFM - Manager name INPUT_RECORD_TYPE is Record Type. The PFM - View names are useful when specifying fields on the GUI of PFM - Web Console.

PFM - Web Console

One of the program products comprising Performance Management. PFM - Web Console provides the web application server functions necessary for centrally monitoring the Performance Management system from a web browser. PFM - Web Console has the following functions:

• GUI display

• Integrated monitoring and management functions

• Report and alarm definition

physical host

The environment specific to each server that makes up a cluster system. The physical host environment cannot be taken over to another server when failover occurs.

PI record type

See Product Interval record type.

PL record type

See Product Log record type.

probe

A function for executing measurement (for measuring an Internet service's response performance).

Probe action condition definition file (esp.conf)

A file containing the Probe Daemon's start option settings. This file is read when the Probe Daemon starts. The Probe action condition definition file contains start option settings, such as the maximum number of measurement conditions for a probe and the maximum size of a report file.

Probe Daemon

A service for measuring service responsiveness.

Product Detail record type

The record type that stores the performance data that indicates the system status at a given point in time, such as detailed information on the processes that are currently active. Use the PD record type when you want to determine the system statuses at a given point in time, such as those listed below:

• System's operating status

• Capacity of the file system currently being used

product ID

The 1-byte identifier that indicates the Performance Management program to which the service belongs. It is part of a service ID.

Product Interval record type

The record type that stores the performance data for a specific duration (interval), such as the number of active processes during every minute. Use the PI record type when you want to analyze the changes and trends in the system status over time, such as those listed below:

• Trend in the number of system calls that occurred within a specific time span

• Trend in the capacity of the file system being used

Product Log record type

The record type that stores the log information on applications that are being executed or databases being used on UNIX.

real-time report

A report indicating the current status of the monitoring target.

record

A group of operation information entries categorized by their purpose. A monitoring agent collects operation information from each record. The types of records that can be collected vary depending on the agent program.

report

A report defines the information to be used when graphically displaying the performance data collected by PFM - Agent. A report mainly defines the following types of information:

• Records to be displayed in a report

• Performance data display items

• Performance data display format (table, graph, or the like)

report file

A file used to store measurement results temporarily. The output format is CSV, with each row containing a single measurement result. If measurements extend over a specific period of time, results are output to this file for as many measurements as are executed. In the report file, the most recent value is collected by Agent Collector and managed in record format.

service ID

A unique ID assigned to the service of a Performance Management program. For example, to use a command to check the system configuration of Performance Management or to back up the performance data of individual agents, you specify the service ID of the Performance Management program and execute the command. The format of the service ID differs depending on whether the product name display functionality is enabled. For details about the service ID format, see the chapter explaining the Performance Management functions in the JP1/Performance Management Planning and Configuration Guide.

service type

A number indicating the type of an Internet service or user-defined service supported by PFM - Agent for Service Response.

single-instance record

A record that is recorded in a single line. Such records do not have a specific ODBC key field.

See Instance.

stand-alone mode

The mode in which PFM - Agent is running alone. Even when the Master Manager service and Name Server service of PFM - Manager cannot be started because of an error, you can start PFM - Agent alone and collect performance data.

status management function

A function for managing the statuses of all services that run on PFM - Manager and PFM - Agent. The status management function enables the system administrator to correctly determine the service startup and stop statuses at each host, making it possible to take the appropriate error recovery measures.

Store database

The database that stores the performance data collected by the Agent Collector service.

Trap Generator

One of the PFM - Manager services. It is a service that issues SNMP traps.

user-defined command

A program created to measure a service other than the standard Internet services supported by PFM - Agent for Service Response. One user-defined command can measure a single measurement item.

user-defined service

A service other than the standard Internet services supported by PFM - Agent for Service Response. The user can measure a user-defined service by creating a user-defined command, and then registering it into PFM - Agent for Service Response.

user-defined service ID

A unique number assigned to a measurement condition for a user-defined service, for management purposes. Each user-defined service ID must be unique, because it is used as the identifier of the measurement condition.

Web Recorder

A GUI used for defining Web transaction information and measurement conditions.

Web Recorder action condition definition file

A file containing Web Recorder's operating condition settings. It is read when Web Recorder starts.

Web transaction file

A file used to define information needed for Web transaction measurement, such as the following: the URL to be accessed by a target Web transaction, Web authentication, and a proxy. This file is read when the Probe Daemon starts.

Web transaction measurement

For measurement of an HTTP(S) service, a single set of a request and a response can be managed, as can a transaction consisting of multiple HTTP(S) requests and responses. To measure a Web transaction, a Web transaction file is created to define information about the Web transaction. Then HTTP(S) requests are issued according to that definition to measure response performance, such as the response time. Playback and measurement of a transaction are achieved by simulating a series of operations using a browser software (such as Internet Explorer). Web transaction measurement supports measurement of an entire Web transaction, measurement of response performance in any given page transition, and error detection in the measurement target by checking the response during transaction measurement processing.

Non-interactive (command)

Command execution method in which operator input required for command execution are provided by values in option specifications or in definition files.

Executing a command non-interactively saves work when configuring an operation monitoring system and can reduce user workload.

To Page Top