10.3.2 Log files and directories to check
This subsection describes the log information that is output from Performance Management programs. For details about the name and size of the file to which the operation status log information is output, see the chapter that describes troubleshooting 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
This subsection describes the trace log, which is one of the types of log information for Performance Management.
The following table lists the output sources and the storage folder names for Windows.
|
No. |
Type of log information |
Output source |
Folder name |
|---|---|---|---|
|
1 |
Trace log |
Action Handler service |
installation-folder\bin\action\log\ |
|
2 |
Performance Management command |
installation-folder\tools\log\ |
|
|
3 |
Remote Monitor Collector service |
installation-folder\agt7\agent\instance-name\log\ |
|
|
4 |
Remote Monitor Store service |
installation-folder\agt7\store\instance-name\log\ |
|
|
5 |
Status Server service |
installation-folder\bin\statsvr\log\ |
|
|
6 |
Trace log (for logical host operation) |
Action Handler service |
environment-folder#\jp1pc\bin\action\log\ |
|
7 |
Performance Management command |
environment-folder#\jp1pc\tools\log\ |
|
|
8 |
Remote Monitor Collector service |
environment-folder#\jp1pc\agt7\agent\instance-name\log\ |
|
|
9 |
Remote Monitor Store service |
environment-folder#\jp1pc\agt7\store\instance-name\log\ |
- #
-
The environment folder is on the shared disk that was specified when the logical host was created.
The following table lists the output sources and the storage directory names for UNIX.
|
No. |
Type of log information |
Output source |
Directory name |
|---|---|---|---|
|
1 |
Trace log |
Action Handler service |
/opt/bin/action/log/ |
|
2 |
Performance Management command |
/opt/jp1pc/tools/log/ |
|
|
3 |
Remote Monitor Collector service |
/opt/jp1pc/agt7/agent/instance-name/log/ |
|
|
4 |
Remote Monitor Store service |
/opt/jp1pc/agt7/store/instance-name/log/ |
|
|
5 |
Status Server service |
/opt/jp1pc/bin/statsvr/log/ |
|
|
6 |
Trace log (for logical host operation) |
Action Handler service |
environment-directory#/jp1pc/bin/action/log/ |
|
7 |
Performance Management command |
environment-directory#/jp1pc/tools/log/ |
|
|
8 |
Remote Monitor Collector service |
environment-directory#/jp1pc/agt7/agent/instance-name/log/ |
|
|
9 |
Remote Monitor Store service |
environment-directory#/jp1pc/agt7/store/instance-name/log/ |
- #
-
The environment directory is on the shared disk that was specified when the logical host was created.
(3) Agent log
This subsection describes the agent log of PFM - RM for Platform, which is one of the types of log information for Performance Management.
The following table lists the output sources, output targets, log file names, and disk space used for Windows.
|
No. |
Type of log information |
Output source |
Output target |
File name |
Default disk space used#1 (megabytes) |
|---|---|---|---|---|---|
|
1 |
Normal log |
PFM - RM for Platform |
installation-folder\agt7\agent\instance-name\log\ |
collect_core_nn#2 |
3 (x 4)#3 |
|
2 |
collect_nn#2 |
||||
|
3 |
timer_core_nn#2 |
||||
|
4 |
timer_nn#2 |
||||
|
5 |
target_monitoring-target-name_nn#2 |
||||
|
6 |
Normal log (for logical host operation) |
PFM - RM for Platform |
environment-folder#4\jp1pc\agt7\agent\instance-name\log\ |
collect_core_nn#2 |
3 (x 4)#3 |
|
7 |
collect_nn#2 |
||||
|
8 |
timer_core_nn#2 |
||||
|
9 |
timer_nn#2 |
||||
|
10 |
target_monitoring-target-name_nn#2 |
- #1
-
You can use the following methods to check and change the maximum file size for the agent log:
• jpcconf inst command
• Remote Monitor Configuration property in the PFM - Web Console window
For details about how to change the maximum file size with the jpcconf inst command, see 3.6.2 Updating an instance environment.
- #2
-
The agent log uses the sequential method. First, log information is output to a log file with a file name ending with 01. When the size of the log file reaches the maximum limit, the end of the log file name changes from 01 to 02, and a new log file with a file name ending with 01 is created. After that, log information is output to the log file with the file name ending with 01. If a log file with a file name ending with 02 or higher already exists, that file is overwritten. The latest log data is always output to a log file with a file name ending with 01.
In the file name, nn indicate a number from 01 to 04.
- #3
-
The value in parentheses is the number of log files. For example, 3 (x 4) indicates that a maximum of four log files, each with a size of 3 megabytes, can be created. In this case, the total available disk space must be 12 megabytes.
Use the following formula to estimate the amount of disk space used by agent logs per instance. The units are megabytes.
(4 + number-of-monitored-hosts) x 4 x Log_Size-value-specified-for-the-instance-environment
- #4
-
The environment folder is on the shared disk that was specified when the logical host was created.
The following table lists the output sources, output targets, log file names, and disk space used for UNIX.
|
No. |
Type of log information |
Output source |
Output target |
File name |
Default disk space used#1 (megabytes) |
|---|---|---|---|---|---|
|
1 |
Normal log |
PFM - RM for Platform |
/opt/jp1pc/agt7/agent/instance-name/log/ |
collect_nn#2 |
3 (x 4)#3 |
|
2 |
timer_nn#2 |
||||
|
3 |
target_monitoring-target-name_nn#2 |
||||
|
4 |
Normal log (for logical host operation) |
PFM - RM for Platform |
environment-directory#4/jp1pc/agt7/agent/instance-name/log/ |
collect_nn#2 |
3 (x 4)#3 |
|
5 |
timer_nn#2 |
||||
|
6 |
target_monitoring-target-name_nn#2 |
- #1
-
You can use the following methods to check and change the maximum file size for the agent log:
• jpcconf inst command
• Remote Monitor Configuration property in the PFM - Web Console window
For details about how to change the maximum file size with the jpcconf inst command, see 3.6.2 Updating an instance environment.
- #2
-
The agent log uses the sequential method. First, log information is output to a log file with a file name ending with 01. When the size of the log file reaches the maximum limit, the end of the log file name changes from 01 to 02, and a new log file with a file name ending with 01 is created. After that, log information is output to the log file with the file name ending with 01. If a log file with a file name ending with 02 or higher already exists, that file is overwritten. The latest log data is always output to a log file with a file name ending with 01.
In the file name, nn indicate a number from 01 to 04.
- #3
-
The value in parentheses is the number of log files. For example, 3 (x 4) indicates that a maximum of four log files, each with a size of 3 megabytes, can be created. In this case, the total available disk space must be 12 megabytes.
Use the following formula to estimate the amount of disk space used by agent logs per instance. The units are megabytes.
(2 + number-of-monitored-hosts) x 4 x Log_Size-value-specified-for-the-instance-environment
- #4
-
The environment directory is on the shared disk that was specified when the logical host was created.