Hitachi

JP1 Version 12 JP1/Performance Management Planning and Configuration Guide


1.1.2 Using Performance Management for operation monitoring and the performance data that can be collected

Performance Management is a series of products that centrally monitors the operating status of resources such as database servers and application servers.

Performance Management can acquire detailed information by placing the appropriate agents throughout the system according to the items being monitored, allowing for a highly detailed operation monitoring system.

Performance Management provides a variety of agent products corresponding to specific monitoring targets and products for analyzing the operating information. Performance Management can be deployed easily in an existing system by adding only the necessary monitoring agents that match the existing system environment. Also, in addition to monitoring resources in real time during system operation, Performance Management can gather and store performance data associated with system resources. Analysis of this stored data can serve as a useful tool for ascertaining the operating status of the system in its entirety or improving the performance of the system over the long term.

Figure 1‒4: Operation monitoring using Performance Management

[Figure]

As shown in the figure above, by using Performance Management, the system administrator can collect and centrally manage performance data even in distributed system environments that contain a wide variety of products, without needing to address the differences between platforms.

Table 1‒1: Examples of performance data that can be collected

Monitoring target

Collected performance data

OS

Windows

CPU usage, available memory, disk status, network status, and device information

HP-UX, Solaris, AIX, Linux

CPU usage, available memory, disk status, and amount of network data transferred

Database server

Oracle

Database usage, SQL information, and parameter information

SQL Server

CPU usage, database use, cache hit rate, and lock information

DB2

Memory usage, sort information, error information, and configuration parameter information

HiRDB

Number of transactions, number of log input/output errors, and HiRDB file system base usage

Distributed transaction manager

OpenTP1

Transaction information, RPC call, schedule information, and journal acquisition status

Job management

JP1/AJS

Number of jobs started, number of delayed jobs, number of held jobs, and length of time on hold

Web server

IIS

Web connection failure (Not Found error) status, ASP request execution time, and session information

Web application server

Cosminexus

Java heap usage, OS resources consumed by J2EE servers, EJB operating information, and Web container operating information

WebLogic Server

Thread pool information and EJB operating information

WebSphere Application Server

Thread pool information, EJB operating information, and Web container operating information

Service response management

Internet services

Response times for protocols such as HTTP, SMTP, FTP, and TCP

ERP

SAP R/3

Roll area usage (SAP memory), response time, and system log/CCMS alerts

Groupware

Lotus Notes/Domino

Notes log (log.nsf) collection, Notes mail occurrence status, LDAP detail status, and status of replication execution by a replicator

Exchange Server

Queue/messages, user logon information, and unused e-mail boxes

Message queuing

WebSphere MQ

Queue information, queue manager information, information about handles that are accessing the queue, and channel information

Virtual environment

VMware

The following performance data for the physical server and for each virtual machine:

  • CPU usage

  • Disk I/Os

  • Disk usage

  • Memory usage

  • Amount of network data transferred

Hyper-V

  • The following performance data for the physical server and for each virtual machine:

    • CPU usage

    • Disk I/Os

    • Memory usage

    • Amount of network data transferred

  • The following performance data for the physical server

    • Disk usage

Hitachi Compute Blade logical partitioning feature

  • The following performance data for physical servers and for each virtual machine:

    • CPU usage

    • Disk I/O

    • Network data traffic

  • The following performance data for physical servers:

    • Memory usage

KVM

  • The following performance data for the physical server and for each virtual machine:

    • CPU usage

    • Disk I/Os

    • Memory usage

    • Amount of network data transferred

  • The following performance data for a physical server

    • Disk usage

For details about the performance data that can be collected, see the PFM - Agent or PFM - RM manuals.