Generating an audit report of health investigations for a server
You can generate an audit report that shows all of the health investigations for your
server inventory in comma-separated value (CSV) format.
Before you begin
You must have a user profile with the Manage investigations
permission or the View investigations permission. For more information, see
Configuring roles
and permissions.
Choose a server by clicking the server name in the Server column on the
Security page or Server management page, then click the
Health investigations tab in the server details page.
Figure 1. Example Server health investigations page with a list of health
investigations for a server
If you do not see a listing of investigations, you have insufficient permissions. For more
information about permissions, see Roles and
permissions.
Click Download audit report.
In the system dialog that opens, you can open or save the audit report to your local
computer.
Open the audit report by using a program capable of viewing CSV files, such as a spreadsheet
editor.
The data looks similar to the following image:Figure 2. Viewing example audit report of security status of servers in CSV format
Note the column headings:
Investigation number
A sequential number that uniquely identifies the investigation.
Investigation ID
A unique identifier for the health investigation.
Status
The status of the health investigation.
Problem detected
Conditions on the managed server suggest a problem that might affect server performance or
stability, but an investigation is not started. The type of problem is listed in the
Investigation type column. An investigation in this state cannot be deleted.
Under normal operating conditions, the status of this investigation changes to Investigating in less
than 1 minute.
Investigating
WebSphere Automation is gathering information from the managed
server. The process of investigating an issue might require only a few minutes or several
hours.
Investigation complete
The analysis of the problem on the managed server is finished. Click the investigation to view
more details about the problem and possible next steps. Expand View history
for more details about each step in the investigation. You can download the files that were created
for this investigation.
Investigation failed
The analysis of the problem on the managed server did not complete. Expand View
history to see which investigation steps completed and which one was unsuccessful. If
any files were created for this investigation, you can download them.
Server
The name of the server.
Hostname
The hostname of the server.
Topology
The server topology. For WebSphere Application Server, the topology refers to
the cell and node configuration. For WebSphere Application Server Liberty, the topology
is the user directory.
Installation directory
The directory where the server software is installed.
Investigation method
The reason for the health investigation. Possible values are Manual (if started
by a user) and Automated (as a result of a detected problem).
Investigation type
The type of issue that is under investigation.
Initiation/detection time
The time that the health investigation started, in ISO standard yyyy-MM-dd HH:MM:SS
AM/PM (UTC time) format. The editor that you import the data into might convert the date to
a different format.
Completion time
The time that the health investigation completed, in ISO standard yyyy-MM-dd HH:MM:SS
AM/PM (UTC time) format. The editor that you import the data into might convert the date to
a different format.
Summary
A summarized description of the status or result of the health investigation.
Note the column headings: