7.3.1 Types of log information
- Organization of this subsection
(1) System log
A system log contains log information that describes the system status and reports errors in the system. System logs are output to the following log files:
-
In Windows
Event log file
For details about the output format, see the chapter on log information in the manual JP1/Performance Management Reference.
- Cautionary note on logical host use
-
In addition to the system log for Performance Management, logs for the cluster software are required. Use these logs to check the instructions issued to Performance Management by the cluster software.
(2) Common message log
The common message log contains log information that describes the system status and reports errors in the system. The common message log contains information that is more detailed than that in the system log. For details about the output file name and file size of the common message log, see 7.3.2 List of log files and directories. For details about the output format of the common message log, see the chapter on log information in the manual JP1/Performance Management Reference.
- Cautionary note on logical host use
-
When Performance Management is set up for logical host use, the common message log is output to a shared disk and inherited at failover. This means that the messages are recorded in the same log file before and after failover.
(3) Operation status log
The operation status log contains log information output by PFM - Web Console. For details about the output file name and file size of the operation status log, see the chapter on troubleshooting in the JP1/Performance User's Guide. For details about the output format of the operation status log, see the chapter on log information in the manual JP1/Performance Management Reference.
(4) Trace log
A trace log contains log information that helps you investigate the status of the system leading up to the problem, and measure the processing time for each process.
Trace logs are output to the log files belonging to each Performance Management service.
- Cautionary note on logical host use:
-
When Performance Management is set up for logical host use, trace logs are output to the shared disk and inherited at failover. This means that the messages are recorded in the same log file before and after failover.
(5) Agent log
An agent log that is output by PFM - Agent for Microsoft SQL Server contains log information about the processing executed to acquire records. If a problem occurs, collect agent logs to acquire detailed information about the processing.
Agent logs are output to separate files according to its type: normal log or error log. For details about output destinations, see 7.3.2(3) Agent log.
- Format:
-
The format of an output agent log is as follows:
yyyy/mm/dd hh:mm:ss.sss agtq PID inf1 inf2 inf3 MessageID Message
The following explains the output items.
Table 7‒2: Agent log items Item
Description
yyyy/mm/dd
Date on which the log was output (yyyy: year, mm: month, and dd: day)
hh:mm:ss.sss
Local time at which the log was output (hh: hour, mm: minute, ss: second, and sss: millisecond)
agtq
Name of the process that output the log (agtq is the process name of PFM - Agent for Microsoft SQL Server).
PID
Output process ID
inf1 to inf3
Maintenance information
MessageID
Message ID#
Message
Message#
- #
-
For details about the message contents, see 6. Messages.
- Notes
-
-
Do not change the time set on the Agent host or the update time of an agent log file. Since information about the last update date and time is used to output agent logs, the agent logs may not be output correctly if these times are changed.
-
When Performance Management is set up for logical host use, specify a path on the shared disk so that the agent log output destination is the same for both the executing node and the standby node.
-