How to enable Agent logging in Tivoli Performance Analyzer
ShaunR 2700005SW1 Visits (6941)
So in the first blog we looked at setting ITPA tracing on the TEP, now we're going to look at the actual agent. The steps are much the same, but you need to be aware that enabling this logging will have a noticeable impact on the performance of the agent. It's recommended that you only use it when solving a problem, and like with any sort of DEBUG logging in ITM, you switch it off afterwards. Don't just leave it on all the time.
Here's the steps you need to follow to set this, again please don't do this unless we've specifically said we need it!
The log files for the agent are created in the directory $ITM
1. Stop the Performance Analyzer agent.
* On Windows platforms, click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services, then right-click on Performance Analyzer and select Stop.
* On other platforms, enter the following command: 'itmcmd agent stop pa'
2. Open the init.cfg file. Depending on your operating system, the file will be located in the following directories:
3. Update the LogLevel and LogSize parameters:
4. Start the Performance Analyzer agent.
-On Windows platforms, click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Monitoring
Services, then right-click on Performance Analyzer and select Start.
-On other platforms, enter the following command: 'itmcmd agent start pa'
Logging with debugging is now enabled for the agent.
5. Wait until the message 'Waiting for a period of 60000' appears in the kpacma.log file. The message means that the processing cycle of the agent is over.
6. If you want to send the log files to support, stop the agent, compress the kpacma*.log files to itpa_agent_log1.zip and send it.
7. Restore the default values to the LogLevel and LogSize parameters:
8. Restart the agent.
And that's that. Again, pretty straightforward but I'm going to say it one more time - Please don't just turn this on and forget about it! We do have a fair few customers who enable debug logging for ITM OS agents and then just leave it on. You're going to generate logs filled with crap, and you're going to see your agents take a performance hit. I'll stop harping on about it now.
Thanks again for taking the time to read this blog about the black sheep of the ITM family (or is that TCR?) and I hope some of you find this useful.
Subscribe and follow us for all the latest information directly on your social feeds: