RE: ITM Agents Logging Event Dectection in Milliseconds

Hey Julius, To make things clearer, my question has nothing to do with sampling.  I'm looking to configure the Global and Local timestamps fore events to display milliseconds as well.    Regards,



Gregory R. Mendes
770-317-8593

 Date: Fri, 15 Feb 2013 17:58:45 +0100
From: [email protected]
To: [email protected]
Subject: Re: [TME10] ITM Agents Logging Event Dectection in Milliseconds

On Fri, Feb 15, 2013 at 10:49:12AM -0600, Gregory Mendes
<[email protected]> wrote:
> 
> Hey John, Thanks for that information but I wasn't asking about sampling
> intervals.  What I need to know but can't seem to find in any *.env, *.ini,
> *.properties, etc,  can the Local and Global Timestamps caputure or be
> configured in milliseconds when an event is sampled.  So, when the ITM agent
> detects the event the requirement is to store that in the log file in
> HH:MM:SS:millisecond and not HH:MM:SS. Regards,
What sense does it make when the shortest sampling interval is one second?
Adding milliseconds won't add any precision.
 
Although I'm not exactly sure if you are talking about timestamps in attribute
groups or in agent logs. 
> 
> 
> 
> Gregory R. Mendes
> 770-317-8593
> 
>  To: [email protected]
> Subject: Re: [TME10] ITM Agents Logging Event Dectection in Milliseconds
> From: jalvord-r/[email protected]
> Date: Fri, 15 Feb 2013 08:32:25 -0800
> 
> 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] 		 	   		  
 
> _______________________________________________
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]
 
 
-- 
 
[ Julius Loman ][ [email protected] ][ http://lomo.kyberia.net ][ icq:35732873 ]
 

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

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