Re: ITM Agents Logging Event Dectection in Milliseconds

For sampled situations, the minimum re-evaluation interval is 30 seconds*.

For pure situations like Unix Log Agent, the logs are rechecked every 
second.

I am not sure how to answer their need... at a millisecond level. most 
measured items are running at 0% or 100%... 

I suspect they have not though through all the issues.

* I know how to tweak a situation to change that lower - not with 
Situation Editor... but 1 second is the minimum. At that level the Agent 
might be consuming 50-80% of the system CPU - which does not sound 
practical.

Regards, 

  



John Alvord - Ph: 1-720-396-2788    Cell: none 
Customer Support - Tivoli Software - jalvord-r/[email protected]
Advisory Engineer - Tivoli Monitoring - ITM infrastructure
Follow us on Twitter! @Tivolisupport and Facebook
Personalize your support needs with the IBM Support Portal
Use Service Request to get assistance!
For emails regarding a PMR, copy [email protected]
For secure browser uploads: https://www.ecurep.ibm.com/app/upload
For Customer Support guidance: IBM Software Support Handbook









From:   Gregory Mendes <[email protected]>
To:     <[email protected]>, 
Date:   02/15/2013 07:58 AM
Subject:        [TME10] ITM Agents Logging Event Dectection in 
Milliseconds
Sent by:        [email protected]



Hello All,
 
I have a customer that has a requirement for millisecond logging of ITM 
agent events when they occur.  I know that the Linux OS Agent and the Disk 
I/O situation  can monitor in milliseconds.  However, the real requirement 
is when an ITM agent detects a situation of any type, can it log that 
detection in a log file in milliseconds.  I only see HH:MM:SS from local 
and global timestamps.
 
Regards,

Gregory R. Mendes
770-317-8593
_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]