Performance Analyzer -Some Best Practices
Kiran Shashi 2700069WSG Visits (2662)
The Performance Analyzer agent is another component that gets installed as part of the ITM base components, This agent has the ability to analyze the historical data in the Tivoli Data Warehouse for several agents like OS, VMware, ITCAM, DB2 and Oracle.
Typically after the installation of the ITPA component with the base ITM the user would install the ITPA Domain and Reports add-on - without which the Performance Analyzer agent is meaningless.
Out-Of-Box Task Configurations.
Performance Analyzer comes with a set of default tasks, and is configured to run out-of-the-box after the installation. They are operational, however the user has to check that the Historical Collection for the particular agent is configured to the Tivoli Data Warehouse. ( this is the pre-requisite)
User would click on the Historical Collection icon on the TEP GUI and bring up the interface to configure the agent first. In this case I will show how the Linux OS agent is being configured.
Let's look at the Linux Agent, Here I have configured some attributes like the CPU, Disk, Network for Historical collections.
The Summarization and Pruning is described in detail in this IBM reference.
Next., click on the Tivoli Performance Agent domain for OS agent and configure Summarization and Pruning attributes. ( these are my samples )
The tasks are all set to Active state to begin with, and Run at startup meaning the tasks will be run the first time ITPA is started and then later on at every Task interval ( in this case above -it will run every day at the same time - this was started )
This is the Out-of-the-box task configuration.
With this, and after a good few iterations ( .e.g; after 2- days ) the Trends and Graphs on the Performance Analyzer can be seen, but since the ITPA also reports on how the forecasts will be like in 7 days, 30days, and 90 days, looking at the data with just one or 2 days of data is not going to be meaningful.
One would wait for first few days ( say a week) before the PA graphs for trend and forecasts would make sense.
This description is good if the Task Interval is set to 1 day.
(to be continued )
I have tried to not make too many configuration changes - as I want to describe the out-of -the box task configuration here.
But , if you would like to see some trending data earlier - then one would let the tasks run at a closer interval, say once every hour or so - to just get started and see some graphs. ( this is not recommended - but I do it sometimes to see if the data is getting analyzed )