9.4.1 Data to be collected from a Windows environment
- Organization of this subsection
(1) Log information about the OS
The following table lists the log information about the OS that needs to be collected.
No. |
Type of information |
Overview |
Default file name |
Collection by the jpcras command |
---|---|---|---|---|
1 |
System log |
Windows event log |
-- |
Y |
2 |
WMI log |
system-folder\system32\WBEM\Logs\*# |
Y |
|
3 |
Process information |
List of processes |
-- |
Y |
4 |
System file |
hosts file |
system-folder\system32\drivers\etc\hosts |
Y |
5 |
services file |
system-folder\system32\drivers\etc\services |
Y |
|
6 |
OS information |
System information |
-- |
Y |
7 |
Network status |
-- |
Y |
|
8 |
Host name |
-- |
Y |
|
9 |
Windows firewall information |
-- |
Y |
|
10 |
Dump information (in Windows Server 2003) |
Dr. Watson log file |
system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log# system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dump# |
Y |
11 |
Dump information (in Windows Server 2008 or Windows Server 2012) |
Problem report and solution log file |
user-mode-process-dump-output-folder\program-name.process-ID.dmp Example: jpcagt7.exe.2420.dmp |
N |
(2) Information about Performance Management
The following table lists the Performance Management information that needs to be collected. In the case of a network connection error, you must also collect applicable files from the machine at the connection destination.
No. |
Type of information |
Overview |
Default file name |
Collection by the jpcras command |
---|---|---|---|---|
1 |
Common message log |
Message log output from Performance Management (sequential file method) |
installation-folder\log\jpclog{01|02}#1 |
Y |
2 |
Message log output from Performance Management (wrap-around file method) |
installation-folder\log\jpclogw{01|02}#1 |
Y |
|
3 |
Configuration information |
Each configuration information file |
-- |
Y |
4 |
Output results of the jpctool service list command |
-- |
Y |
|
5 |
Version information |
Product version |
-- |
Y |
6 |
Historical information |
-- |
Y |
|
7 |
Database information |
Remote Monitor Store service |
|
Y |
8 |
Trace log |
Trace information for each service of the Performance Management program |
--#2 |
Y |
9 |
Agent log |
Normal log of the processing related to record collection by PFM - RM for Platform |
|
Y |
10 |
Work data |
Work data during performance data collection |
|
Y |
11 |
Install log#3 |
Message log during installation |
|
N |
12 |
Language environment information for system account |
Language environment information for system account |
|
Y |
(3) Software information
The following table lists the types of information that must be collected by the various software when you want to use PFM - RM for Platform to collect performance data.
No. |
Type of information |
Overview |
Acquiring command |
Collection by the jpcras command |
---|---|---|---|---|
1 |
PuTTY |
SSH client (plink) version information |
plink.exe -V#1 |
Y |
2 |
ActivePerl |
Perl module (perl) version information |
perl.exe -V#2 |
Y |
(4) Operation information
You need the following information about the operation that was underway when an error occurred:
-
Details of the operation
-
Time the error occurred
-
Machine configuration (such as the version of each OS, host name, and configuration of PFM - Manager and PFM - RM for Platform)
-
Whether the problem is repeatable
-
Performance Management user name used during logon, if the user has logged on from PFM - Web Console
-
Any arguments specified in a command, if the problem occurred during command execution
(5) Error information on screen displays
Obtain a hardcopy of the following information:
-
The window operation when the application error occurred
-
The error message dialog box (including the contents of detailed information if displayed)
-
The Command Prompt window or the Administrator Console window, if the error occurred during command execution
(6) User-mode process dump (in Windows Server 2008 or Windows Server 2012)
In a Windows Server 2008 or Windows Server 2012 environment, if a Performance Management process is stopped by an application error, collect a user-mode process dump.
(7) Collecting a problem report (in Windows Server 2008 or Windows Server 2012)
In a Windows Server 2008 or Windows Server 2012 environment, if a Performance Management process is stopped by an application error, collect a problem report.
(8) Other information
You also need the following information:
-
The contents of System and Application in the Event Viewer window of Windows
-
The contents of System Information, which is displayed by choosing Accessories, and then System Tools