Configure Tivoli Performance Viewer settings

Network Deployment (Distributed operating systems), v8.0 > Monitor > Monitor overall system health > Monitor performance with Tivoli Performance Viewer > View current performance activity

Configure Tivoli Performance Viewer settings

Overview

TPV monitors the performance activity of all servers on a node. Changing TPV settings can affect performance.
Activity monitoring can be configured on a per-user basis where any changes made...

are only for the server being monitored
only affect the user viewing the data

Configure TPV user settings

From the console go to...

Monitor and Tuning | Performance Viewer | Current Activity | server_name | Settings | Sets | User

...and set...

Refresh Rate How frequently TPV collects performance data from PMI. Default is 30 seconds. Range is 5 to 500 seconds. A large value is useful for long-running load and performance tests
Buffer Size Number of entries to be stored for a server. Data displayed in TPV is stored in a short in-memory buffer. After the buffer is full, each time a new entry is retrieved the oldest entry is discarded. The default buffer size is 40 entries. Supported values are 10, 20, 30, 40, 50, 60, 70, 80, 90 and 100. The larger the buffer size, the more memory is consumed. Thus, specify a buffer size that allows you capture enough monitoring data for analysis without wasting memory storing unneeded data.
View Data As

Raw Value Display absolute value. If the counter represents load data, such as the average number of connections in a database pool, then TPV displays the current value followed by the average. For example, 18 (avg:5).
Change in Value Display change in the current value from the previous value.
Rate of Change Display ratio change/(T1 - T2), where change is the change in the current value from the previous value, T1 is the time when the current value was retrieved, and T2 is the time when the previous value was retrieved.

The refresh rate and buffer size settings combine to control how much temporal history we have for the application server. The default values for Refresh Rate (30 seconds) and Buffer Size (40 entries) provide you with a 20-minute history of the application server's performance. Changing one of these parameters affects the length of the temporal history.
The values you set for Refresh Rate and Buffer Size depend on your use of TPV.
To diagnose a known problem on a test machine, you might poll data more frequently while having a decreased buffer size.
To monitor a production server, you might poll data less frequently and specify a buffer size depending on how much history you want. However, TPV is not intended to be a full-time monitoring solution.

Configure TPV log settings

Beforing clicking the Start Logging link, go to...

Monitor and Tuning | Performance Viewer | Current Activity | server_name | Settings | Sets | Log

...and set...

Duration Length of time, in minutes, that logging continues, unless Stop Logging is clicked first. TPV is not intended as a full-time logging solution.
Maximum File Size Maximum size, in megabytes, of a single file. Note that TPV automatically zips log files to save space and this parameter controls the pre-zipped file size and not the post-zipped, which is smaller.
Maximum Number of Historical Files Number of files TPV writes before stopping. If TPV reaches the maximum file size before the logging duration ends, it continues logging in another file, up to the maximum. If TPV reaches the maximum number of historical files before the logging duration ends, TPV deletes the oldest historical file and continues logging in a new file. The total amount of data stored is constrained by...

Maximum File Size
Maximum Number of Historical Files

File Name Name of the log file. The server name and the time at which the log is started is appended to the log name to help users identify a log file.
Log Output Format Whether TPV writes log files as XML or in a binary format. Binary format provides a smaller log file when uncompressed and is recommended if space is a consideration.

View current performance activity
Monitor performance with TPV
View Data with the TPV
Select a server and changing monitoring status

+
Search Tips | Advanced Search

Duration	Length of time, in minutes, that logging continues, unless Stop Logging is clicked first. TPV is not intended as a full-time logging solution.
Maximum File Size	Maximum size, in megabytes, of a single file. Note that TPV automatically zips log files to save space and this parameter controls the pre-zipped file size and not the post-zipped, which is smaller.
Maximum Number of Historical Files	Number of files TPV writes before stopping. If TPV reaches the maximum file size before the logging duration ends, it continues logging in another file, up to the maximum. If TPV reaches the maximum number of historical files before the logging duration ends, TPV deletes the oldest historical file and continues logging in a new file. The total amount of data stored is constrained by... Maximum File Size Maximum Number of Historical Files
File Name	Name of the log file. The server name and the time at which the log is started is appended to the log name to help users identify a log file.
Log Output Format	Whether TPV writes log files as XML or in a binary format. Binary format provides a smaller log file when uncompressed and is recommended if space is a consideration.