7.3.2 Log file and folder list
This subsection explains the log information that is output by Performance Management programs. For details about the name of the output destination file for the operation status log and the file size, see the chapter that explains error detection in the JP1/Performance Management User's Guide.
- Organization of this subsection
(1) Common message log
For details about the common message log, see the chapter that describes details on log information in the JP1/Performance Management User's Guide.
(2) Trace log
Of the five types of log information that are output by Performance Management, the table below shows the service name or control name that outputs the trace log of PFM - RM for Virtual Machine, and the folder name at the destination where the log is saved.
Log information type |
Output source |
Folder name |
---|---|---|
Trace log |
Action Handler service |
installation-folder\bin\action\log\ |
Performance Management command |
installation-folder\tools\log\ |
|
Remote Monitor Collector service |
installation-folder\agt8\agent\instance-name\log\ |
|
Remote Monitor Store service |
installation-folder\agt8\store\instance-name\log\ |
|
Status Server service |
installation-folder\bin\statsvr\log\ |
|
Trace log (in logical host environment) |
Action Handler service |
environment-folder#\jp1pc\bin\action\log\ |
Performance Management command |
environment-folder#\jp1pc\tools\log\ |
|
Remote Monitor Collector service |
environment-folder#\jp1pc\agt8\agent\instance-name\log\ |
|
Remote Monitor Store service |
environment-folder#\jp1pc\agt8\store\instance-name\log\ |
- #
-
The environment folder is a folder that was specified on the shared disk when the logical host was created.
(3) Collected log
Of the five types of log information that are output by Performance Management, the table below shows log file names, disk usage, and the service name or control name that outputs the collected log of PFM - RM for Virtual Machine.
A collected log is created for each monitoring target.
Log information type |
Output source |
Output destination |
File name |
Default disk usage#1 (megabytes) |
---|---|---|---|---|
Regular log |
PFM - RM for Virtual Machine |
installation-folder\agt8\agent\instance-name\log\ |
VM_Type_monitoring-target-name{1|2|3|4|5|6|7|8}.log#2 |
128 |
installation-folder\agt8\agent\instance-name\targets\monitoring-targetname\log\ |
jpcagt5virtage{1|2|3|4|5|6|7|8}.log#2 |
128 |
||
Regular log (in logical host environment) |
PFM - RM for Virtual Machine |
environment-folder#3 \jp1pc\agt8\agent\instance-name\log\ |
VM_Type_monitoring-target-name{1|2|3|4|5|6|7|8}.log#2 |
128 |
environment-folder#3 \jp1pc\agt8\agent\instance-name\targets\monitoring-targetname\log\ |
jpcagt5virtage{1|2|3|4|5|6|7|8}.log#2 |
128 |
- #1
-
The maximum file size of the collected log can be checked or modified using the following procedures:
-
Execute the jpcconf inst setup command.
-
View the Remote Monitor Configuration property in the PFM - Web Console window.
For details about the procedure that uses the jpcconf inst setup command, see 2.4.2 Updating an instance environment.
-
- #2
-
The collected log uses the wrap-around file method. This method adds data to the latest log, without deleting the existing log. When the file size of a log exceeds the specified size, a new file with the log file number incremented by one is created. When the maximum number of logs that can be generated is reached (fixed at 8), the first file is overwritten.
- #3
-
The environment folder is a folder that was specified on the shared disk when the logical host was created.