17.5.1 Data to be collected in the event of trouble (in Windows)
- Organization of this subsection
(1) Log information about the OS
The following table lists the log information about the OS to be collected.
Type of information |
Outline |
Default file name |
Collected by the jpcras command |
Collected by the jpcwras command |
---|---|---|---|---|
System log |
Windows event log |
N/A |
Y |
Y |
Process information |
List of processes |
N/A |
Y |
Y |
System file |
hosts file |
system-folder\system32\drivers\etc\hosts |
Y |
Y |
services file |
system-folder\system32\drivers\etc\service |
Y |
Y |
|
OS information |
System information |
N/A |
Y |
Y |
Network status |
N/A |
Y |
Y |
|
Host name |
N/A |
Y |
Y |
|
Firewall information |
N/A |
Y |
N |
|
Dump information |
Log files regarding problem reports and solutions |
output-destination-folder-for-user-mode-process-dump\program-name.process-ID.dmp Example: jpcagtt.exe.2420.dmp |
N |
N |
- Legend:
-
Y: Can be collected
N: Cannot be collected
N/A: Not applicable
- #
-
If your setup provides for output of log files to a different folder, be sure that you collect the data from the correct folder.
(2) Performance Management information
You need to collect the information about Performance Management listed below. In the case of a network error, you also need to collect applicable files from the connection-destination machine. The Performance Management information required to be collected is shown below.
Type of information |
Outline |
Default file name |
Collected by the jpcras command |
---|---|---|---|
Common message log |
Message log output from Performance Management (sequential file method) |
installation-folder\log\jpclog{01|02}#1 |
Y |
Message log output from Performance Management (wrap-around file method) |
installation-folder\log\jpclogw{01|02}#1 |
Y |
|
Common message log (logical host use) |
Message log output from Performance Management (sequential file method) |
environment-directory\jp1pc\log\jpclog{01|02}#1 |
Y |
Message log output from Performance Management (wrap-around file method) |
environment-directory\jp1pc\log\jpclogw{01|02}#1 |
Y |
|
Configuration information |
Each configuration information file |
|
Y |
Database information |
Name Server |
|
Y |
Master Manager |
|
Y |
|
Master Store |
|
Y |
|
View Server |
|
Y#7 |
|
Agent Store and Remote Monitor Store |
|
Y#7 |
|
Agent Store (health check agent) |
|
Y#7 |
|
Database information (logical host use) |
Name Server |
|
Y |
Master Manager |
|
Y |
|
Master Store |
|
Y |
|
View Server |
|
Y#7 |
|
Agent Store and Remote Monitor Store |
|
Y#7 |
|
Agent Store (health check agent) |
|
Y#7 |
|
Trace log |
Trace information of each service in the Performance Management program |
N/A#4 |
Y |
Other files |
Other information files |
|
Y |
Install log#5 |
Message log at the time of installation |
|
N |
%SystemDrive%\Windows\Temp\pfm_reg_history.log |
Y |
- Legend:
-
Y: Can be collected
N: Cannot be collected
N/A: Not applicable
- #1
-
For details on the output format of the log files, see 16.5 Detecting problems by linking with the integrated system monitoring product.
- #2
-
xxxx indicates the service key of each PFM - Agent or PFM - RM. For details on service keys of each PFM - Agent or PFM - RM, see the description of the naming rules in an appendix of the JP1/Performance Management Planning and Configuration Guide.
- #3
-
For a PFM - Agent or PFM - RM monitoring an application program which can start multiple service sets on a single host, there is a folder for each instance.
- #4
-
For details on the trace log storage destination, see 17.4.2 Details on log information.
- #5
-
Collect this information if the installation fails.
- #6
-
Collect these files when installation has failed but the file exists.
- #7
-
Collected only when a directory name, a service key, or the all or data option is specified. If the option is omitted, the file is not collected.
(3) PFM - Web Console information
You need to collect the information about PFM - Web Console listed below. In the case of a network error, you also need to collect applicable files from the connection-destination machine. The PFM - Web Console information required to be collected is shown below.
Type of information |
Outline |
Default file name |
Collected by the jpcwras command |
---|---|---|---|
Web server information |
Server log of Web server or Web container |
N/A |
Y |
Registry information |
Product registry information |
N/A |
Y |
Operation status log#1 |
Message log output from PFM - Web Console |
installation-folder\log\jpcwtracelog-file-number#2.log |
Y |
Message log output from a PFM - Web Console command |
|
Y |
|
File information |
List of PFM - Web Console installation files |
N/A |
Y |
Configuration Info |
PFM - Web Console configuration information |
installation-folder\config\*.* installation-folder\sample\config\*.* |
Y |
PFM - Web Console log information |
(Un)installer log file |
system-folder\TEMP\HCDINST\*.LOG |
N |
- Legend:
-
Y: Can be collected
N: Cannot be collected
N/A: Not applicable
- #1
-
For details on the output format of the operation status log, see the chapter explaining the log information in the manual JP1/Performance Management Reference.
- #2
-
The log file number is the number of output log files, starting from 1.
- Operation status log output
-
The output size of the operation status log (excluding the log for the jpcrpt command) can be set by using logFileSize × logFileNumber in the initialization file (config.xml).
- #3
-
For details about the log output format of the jpcrpt command, see 17.4.2(1)(a) Log output format of the jpcrpt command.
(4) Operation information
You need to collect the following information about the operation being performed when an error occurs:
-
Details of the operation
-
Time the error occurred
-
Machine configuration (for example, the OS version, host name, and PFM - Manager and PFM - Agent or PFM - RM configuration)
-
Whether the error is replicable
-
When logged on from PFM - Web Console, the Performance Management user name at logon
-
Arguments specified in a command if a problem occurred while the command was executed
(5) Error information on window displays
Obtain printouts of the following:
-
The Web browser
-
The window operation when the application error occurred
-
The error message dialog box (including the contents displayed if there is a Details button)
-
Command Prompt or the Administrator Console window if a problem occurred while a command was executed
(6) User mode process dump
Collect a user mode process dump if a Performance Management process stopped due to an application error.
(7) Problem reports
Collect problem reports if a Performance Management process stopped due to an application error.
(8) Docker environment information
If you are using Performance Management in a Docker environment, you have to collect the following Docker environment information:
Type of information |
Outline |
Collected by the jpcras command |
---|---|---|
Docker environment information |
Docker version |
Y |
Docker container list |
Y |
|
Process within the Docker container |
Y |
|
Docker container information |
Y |
- Legend:
-
Y: Can be collected
(9) Other information
You also need to collect the following information:
-
The contents of System Information, which is displayed by choosing Accessories and then System Tools
-
Java VM thread dump
When collecting PFM - Web Console information, collect the Java VM thread dump.
To collect the Java VM thread dump:
-
Execute the following command ten times at three-second intervals.
# installation-directory/CPSB/CC/web/bin/cjdumpweb PFMWebConsole
-
Execute the jpcwras command.
- Note:
-
Because the operation of Java VM becomes unstable when collecting a thread dump, restart the PFM - Web Console service.