Checking COUNTERS with check_nt and/or check_nc_net

[Anthony Montibello]

Hi Giles,

I am glad this was mentioned,
This is actually a issue that I want to elaborate on,

The problem is not the command line,
but the counter itself,
Since a 0 was returned, the command line is fine, if it had an issue command
you would have recieved a -1  (you can test this, just misspel the counter)

the issue here is that counter needs to have 2 samples taken before
reporting the answer back to check_nt.
If the time between the samples is too small it would always report a 0,
if the time is too large it would increase the time that check_nt is waiting
for a result.

Preformance counter in windows uses a 1s delay between samples, NC_Net to
expidite responce time uses a default of 15ms.  I found this value to be
good for most counters. (the performance counter viewer tool I created also
uses 1s )

Solution change the sampledelay to a higher value, This can be done remotly
on the fly, but it must be changed in the startup.cfg for NC_NEt to use it
at startup.

you can do this through check_nc_net use -v CONFIG -l "sampledelay,1000" to
update the delay to a full second or you may find updating to
0.1ssufficient -l "sampledelay,100"

I hope this clears up the issue,
please let me know if anyone needs clarification,
or this topic could always be brought over to the NC_NEt forunm on
sourceforge.
http://sourceforge.net/projects/nc-net


Tony (Author of NC_NEt)

On 9/12/07, Giles Coochey <gcoochey at sapphire.gi> wrote:
>
>  Hello List,
>
>
>
> I've been experimenting with check_nt and check_nc_net (I have Nc_Net
> installed on a test server and have had this same problem with both UNIX
> plugins).
>
>
>
> The server is 2003, English version
>
>
>
> The commands which demonstrate working and not working examples are:
>
>
>
> Not working:
>
>
>
> *# ./check_nc_net -H windowssys -v COUNTER -l "\\MSExchangeMTA\\Disk File
> Deletes/sec"*
>
> *\MSExchangeMTA\Disk File Deletes/sec = 0.00*
>
>
>
> Working:
>
>
>
> *# ./check_nc_net -H windowssys -v COUNTER -l "\\MSExchangeMTA\\Free
> Elements"*
>
> *\MSExchangeMTA\Free Elements = 7.00*
>
>
>
> It seems to me that any COUNTER that has a forwardslash in its name
> returns zero.
>
>
>
> I checked actual values on the server using the local performance counter
> viewer provided with nc_net and the values are not zero.
>
>
>
> These are just examples, but I get the same results for \memory\pages/sec
> and others, it doesn't matter whether I use the ^ notation either.
>
>
>
> I tried googling, but didn't get anything relevant, this is NC_Net_V4.1a
> installed via the MSI package.
>
>
>
> Otherwise, everything seems to be working OK.
>
>
>
> Hope someone has either come across this problem or has some ideas, I
> don't should I should need to escape a "/" should I?
>
>
>
> Thanks
>
>
> Giles
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070912/ccca77e0/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null