12.4.2 Performance Management information to be collected
You need to collect the types of information related to Performance Management that are described below. If the error occurred in network connection, you also need to collect information from the connection destination machine. The following table describes the information related to Performance Management.
|
Information type |
Description |
Default file name |
Collection by the jpcras command possible |
|---|---|---|---|
|
Common message log |
Message log output by Performance Management (sequential file method) |
/opt/jp1pc/log/jpclog{01|02}#1 |
Y |
|
Message log output by Performance Management (wrap-around method) |
/opt/jp1pc/log/jpclogw{01|02}#1 |
Y |
|
|
Configuration information |
Information file for each configuration |
-- |
Y |
|
Output results of the jpctool service list command |
-- |
Y |
|
|
Version information |
Product version |
-- |
Δ |
|
History information |
-- |
Δ |
|
|
Database information |
Agent Store |
|
Y |
|
Trace log |
Trace information on each service of a Performance Management program |
--#2 |
Y |
|
Definition file |
Application definition file (09-00 or earlier) |
/opt/jp1pc/agtu/agent/jpcapp |
Y |
|
Application definition file (10-00 or later) |
/opt/jp1pc/agtu/agent/jpcapp2 |
Y |
|
|
Information about the function for collecting user-specific performance data |
Configuration information |
/opt/jp1pc/agtu/agent/jpcuser/jpcuser.ini |
Y |
|
Debug log |
/opt/jp1pc/agtu/agent/jpcuser/debug/jpcuser_dbg_{01|02|03|04|05}.log |
Y |
|
|
Trace log |
/opt/jp1pc/agtu/agent/jpcuser/log/trace/msglog{01|02} |
Y |
|
|
Public log |
/opt/jp1pc/agtu/agent/jpcuser/log/public/jpclog{01|02} |
Y |
|
|
User data file |
/opt/jp1pc/agtu/agent/jpcuser/userdata/jpcuser_{UPI|UPIB|UPD|UPDB|XUI1|XUI2|XUI3|XUI4|XUI5} |
Y |
|
|
Backup file of the user data file |
/opt/jp1pc/agtu/agent/jpcuser/userdata/jpcuser_{UPI|UPIB|UPD|UPDB|XUI1|XUI2|XUI3|XUI4|XUI5}_bak |
Y |
|
|
Core dump file#3 |
/opt/jp1pc/agtu/agent/jpcuser/core |
Δ#4 |
|
|
Installation log#5 |
Default log of Hitachi PP Installer |
/etc/.hitachi/.hitachi.log /etc/.hitachi/.hitachi.log{01|02|03|04|05} /etc/.hitachi/.install.log /etc/.hitachi/.install.log{01|02|03|04|05} |
N |
- Legend:
-
Y: Can be collected (physical host and logical host).
Δ: Can be collected (physical host only).
N: Cannot be collected.
--: Not applicable
- Note:
-
When a logical host is used, replace /opt with environment-directory.
- #1
-
For details about log file output methods, see the chapter explaining error detection in Performance Management in the JP1/Performance Management User's Guide.
- #2
-
For details about the trace log storage destination directory, see 12.3.2 Log files and directories to check.
- #3
-
In HP-UX, you can use the coreadm command to change the name of a core dump file. After renaming, the jpcras command cannot collect any files whose name does not begin with core. For these files, collect information manually.
- #4
-
Dump information is not collected if systemd-coredump is enabled in Linux.
See the chapter explaining Error Handling Procedures in the JP1/PerformanceManagement User's Guide.
- #5
-
Collect this log if installation fails.