Log performance data with Tivoli Performance Viewer
The Tivoli Performance Viewer (TPV) can store data for system resources, pools and queues, and applications in log files for later retrieval. We can start and stop logging while viewing current activity for a server, and later replay this data. Logging of performance data captures performance data in windows of time so we can later analyze the data.
Before using, configure the TPV log settings. The log settings may affect performance. The TPV logging feature is not intended to be a full-time monitoring solution, but instead for selective data recording for subsequent replay and analysis.
We can study the sequence of events that led to a peculiar condition in the application server.
First, enable TPV logging so performance data generated in the application server persists in a log file stored at a specific location. Later, using the replay feature in TPV, view the performance data that was generated in exactly the same chronological order as it was generated in real time, enabling you to analyze a prior sequence of events.
You do not need to know the syntax and format in which log files are generated and stored. Do not edit log files generated by TPV; doing so will irrecoverably corrupt or destroy the performance data stored in the log files.
We can create and view logs in the administrative console.
Create logs
- Click...
Monitoring and Tuning | Performance Viewer | Current Activity | server_name | Settings | Log
To see the Log link on the TPV page, expand the Sets node of the TPV navigation tree. After clicking Log, the TPV log settings are displayed.
- Click on Start Logging when viewing summary reports or performance modules.
- When finished, click Stop Logging .
Once started, logging stops when the logging duration expires, Stop Logging is clicked, or the file size and number limits are reached. To adjust the settings, see step 1.
By default, the log files are stored in...
profile_root/logs/tpv
...on the node on which the server is running. To change the log file directory, in the administrative console, click...
Monitoring and Tuning Performance Viewer | Current Activity | server_name | Settings | Log
...and specify the new directory in the Server File field.
TPV automatically compresses the log file when it finishes writing to it to conserve space. At this point, there must only be a single log file in each .zip file and it must have the same name as the .zip file.
View logs
We can view multiple logs at a time. After a log has been loaded, return to the View Logs panel to see a list of available logs. At this point, we can load another log.
- Click...
Monitoring and Tuning | Performance Viewer | View Logs
- Select a log file to view using either of the following options:
- Explicit Path to Log File
- Choose a log file from the machine on which the browser is currently running. Use this option if we have created a log file and transferred it to the system. Click Browse to open a file browser on the local machine and select the log file to upload.
- Server File
- Specify the path of a TPV log file on the server.
- Click View Log.
The log is displayed with log control buttons.
- Adjust the log view as needed.
Buttons available for log view adjustment are described in the following table. By default, the data replays at the Refresh Rate specified in the user settings. We can choose one of the Fast Forward modes to play data at rate faster than the refresh rate.
Button Description Rewind Returns to the beginning of the log file. Stop Stops the log at its current location. Play Begins playing the log from its current location. Fast Forward Loads the next data point every three (3) seconds. Fast Forward 2 Loads ten data points every three (3) seconds. TPV automatically compresses the log file when it finishes writing it. The log does not need to be decompressed before viewing it, though TPV can view logs that have been decompressed.
Subtopics
Related tasks
Configure TPV settingsMonitor performance with TPV View Data with the TPV