13.3.1 Types of log information to be collected upon troubleshooting
- Organization of this subsection
(1) System log
The system log contains log information that reports the system status and the errors that have occurred. Performance Management outputs the system log to the event log file.
For details about the output formats, see the chapter that describes log information in the manual JP1/Performance Management Reference.
- Notes about logical host operation:
-
In addition to the system log for Performance Management, you need the log information for the cluster software in order to check information such as the control of Performance Management by the cluster software.
(2) Common message log
The common message log contains log information that reports the system status and errors that have occurred. The information output to this log is more detailed than the system log information. For details about the common message log's output destination file name and file size, see 13.3.2 Lists of log files and folders accessed upon troubleshooting. For details about the output format, see the chapter that describes log information in the manual JP1/Performance Management Reference.
- Notes about logical host operation:
-
When Performance Management is under logical host operation, the common message log is output to the shared disk. Because a log file on the shared disk is inherited together with the system during a failover, messages continue to be recorded in the same log file.
(3) Operation status log
The operation status log is the log information that is output by Web Console. For details about the name and size of the operation status log file, see the chapter that describes troubleshooting in the JP1/Performance Management User's Guide. For details about the output format, see the chapter that describes log information in the manual JP1/Performance Management Reference.
(4) Trace log
When an error occurs, the trace log contains log information that is needed to investigate the cause of the error, or to determine the processing time required by each process.
The trace log is output to a log file for that particular Performance Management program service.
- Notes about logical host operation:
-
When Performance Management is under logical host operation, the trace log is output to the shared disk. Because a log file on the shared disk is inherited together with the system during a failover, messages continue to be recorded in the same log file.
(5) Integrated trace log
The integrated trace log is a collection of trace information output by each program; it is output to a single file by the Hitachi Network Objectplaza Trace Library (HNTRLib2). PFM - Agent for Service Response uses the Hitachi Network Objectplaza Trace Library (HNTRLib2) to output log files.
- Notes about logical host operation:
-
When Performance Management is under logical host operation, the trace log is output to the shared disk. Because a log file on the shared disk is inherited together with the system during a failover, messages continue to be recorded in the same log file.