Sitworld: ITM Permanent Configuration Best Practices

John Alvord, IBM Corporation jalvord@us.ibm.com Draft #1 – 1/16/2020 – Level 1.00000 Follow on twitter Inspiration I am often asked for advice on how to change an ITM process configuration. It could be something simple like adding a diagnostic trace definition. It could be more complex like adding EPHEMERAL:Y to a communication control. There areContinue reading “Sitworld: ITM Permanent Configuration Best Practices”

Sitworld: Introduction

During my normal work. I see many interesting puzzles on how to accomplish useful work in IBM Tivoli Monitoring [ITM]. Often these revolve around situations. Over time I will present some basic education on the subject but first there are some interesting cases that will benefit from some interactions.  So for the moment, I willContinue reading “Sitworld: Introduction”

Sitworld: Event History #8 Situation Events Opening And Closing Frequently

John Alvord, IBM Corporation jalvord@us.ibm.com Draft #1 – 21 April 2018 – Level 1.00000 Follow on twitter Inspiration The Event History Audit project is complex to grasp as a whole. The following series of posts will track individual diagnostic efforts and how the new project aided in the process. This was seen in the Event Audit History Advisory section:Continue reading “Sitworld: Event History #8 Situation Events Opening And Closing Frequently”

Sitworld: Policing the Hatfields and the McCoys

John Alvord, IBM Corporation jalvord@us.ibm.com Draft #1 – 2 May 2016 – Level 0.5000 Follow on twitter Inspiration One more time I had to explain to a customer that you could not have a situation formula that included more than a single multi-row attribute group. They had a worthy goal: they wanted to test for a missingContinue reading “Sitworld: Policing the Hatfields and the McCoys”

Sitworld: Real Time Detection of Duplicate Agent Names

One more time I worked on a case where ITM misbehaved because some agents used duplicate names. This particular case involved “false alerts” where a situation event was observed – a missing process case on a Linux System. When investigated, the Linux System did have that process running and so it was a false positive alert.

Sitworld: Rational Choices for Situation Sampling Intervals

John Alvord, IBM Corporation jalvord@us.ibm.com Inspiration I was working on a customer remote Tivoli Enterprise Monitoring Services [TEMS] performance problem. The remote TEMS was showing high CPU utilization and was crashing every couple days. The TEMS Audit report showed that results data from Agents were flowing in at 8 megabytes a minute. That is roughly 10 timesContinue reading “Sitworld: Rational Choices for Situation Sampling Intervals”

Sitworld: ITM Silver Blaze – Agent Responsiveness Checker

I have a great job. People come to me with puzzles and I get paid to investigate. A recent customer had 400+ Solaris systems running Unix OS Agent at ITM 622 FP5 and earlier levels. By chance they identified a single instance of a Unix OS agent that was not running situations. They were naturally worried there could be other cases.