1) check for a text within the description will slow it down, the other fields 
don't impact the speed that much 

2) the check will only check newer entries (we pass the ID of the last seen 
event to the API call that lists the matching entries) 

3) no 

 

 

Dirk Bulinckx. 

From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Joe 
Barron
Sent: Friday, November 09, 2007 3:26 PM
To: Servers Alive Discussion List
Subject: [SA-list] Yet another Eventlog check question... 

 

Like many, I have some issues with the Eventlog check timing out.  I've got the 
log being checked (system log) on my remote machines trimmed down to 256KB, and 
although I could perhaps go smaller I'd prefer not to if I can avoid it.  So 
I've got a few questions.  :-) 

My first question is this:  Do the various configuration options of the 
eventlog check have any impact on speed?  In other words, I know that the entry 
I'm looking for is a Warning.  However, as I currently have the check 
configured, I'm not specifying that, I'm just specifying the Event ID.  If I 
were to specify a type of "Warning" in addition to specifying the Event ID, 
would it reduce the number of entries "read" by the check, or would it still 
have to parse every single one of them? 

My second question -- if I can get it to set initial values, does it note when 
the last point in the log was for the purpose of efficiency?  IOW, if I've got 
it running once a day, and I clear the log on the first day, and then there are 
40 total entries at check time on the second day, and 85 total entries at check 
time on the third day, how many entries is it parsing on the third day?  85 or 
45? 

My third question -- Is there a way to override the 600 second timeout limit?  
This could be an easy fix if so.

And a general question -- are there any particular configuration techniques I 
haven't thought of which can help speed up the check? 

Thanks,
Joe


To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure 
that they are not send to the list nor to the individual members of the list 
that send a message. Doing this will get you removed from the list. 

To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure 
that they are not send to the list nor to the individual members of the list 
that send a message. Doing this will get you removed from the list. 

Reply via email to