NC_NET 4.4 .....services.exe high CPU

[Lynn Folkes]

This is a follow up to a prior posting.  I was getting high CPU utilization when checking log files that were 16meg and in one case 32meg. I was using the 2.28 client.  The test was to change over to the 4.4 client and see if the results improved.  Well they stayed the same. So I dropped the log files down to 5meg and the high CPU readings stopped.  It does appear to be a issue with how dot net interfaces with services.exe.

[tony]

Sorry for the delay,

I do not get Email notification from this list.

Since the eventLog check was released,
Large logs have been a problem
and it was not wise to check more than one one log per server.

However The new version of NC_NEt Contains EVENTLOG_NEW
this check is very efficient on large logs, but the command syntex changed a bit,
(only positive checks, no NEGATE, 2 delimeters)

Use check_nc_net --help=EVENTLOG_NEW for the full syntex and options.

ANd it allows full regular expressions (with options configurable through the startup.cfg)
It is recomended to make sure your check time overlaps the actual checkinterval by 1 or 2 min,
this way no events accidently slip by.

Also make sure your check interval, and retries  -w and -c are all configured
For instance if the -w and -c are filtering exacly what you need,
Does it need a Retry?
if you are just looking for an error occured so Alert - then No,
IF your looking for Oops something keeps tripping then - Yes

TOny