check_win_net_usage now handles connection errors

Written by Claudio Kuenzler - 2 comments

Published on October 19th 2012 - Listed in Nagios Windows Network Monitoring

---

The Nagios/Monitoring plugin check_win_net_usage just got a bugfix which catches connection errors to the target host.

In todays released version 20121019 the fix has been added and throws an UNKNOWN output when the target host is not reachable or in general when check_nt (used in the background) throws an error.
Thanks go to Hermit who caught the bug and delivered the solution to it.

Besides the plugin itselfm, the documentation also got an update. In the section "How to find the correct name of the network interface" I added the Windows command "typeperf.exe". The previously well working method (check_nrpe -c listCounterInstances -a "Network Interface") doesn't seem to work anymore with newer NSClient++ versions. So I spent some time researching for alternatives and typeperf does the job. The discussion of this issue can be followed in the comments on the article "How to monitor Windows network traffic with Nagios". 

Add a comment

Show form to leave a comment

Comments (newest first)

ck from Zurich, Switzerland wrote on Oct 22nd, 2012:

That's correct. It shows the _current_ up and down bandwidth of the interface. I personally check the interface every 3 min and nagiosgraph creates the average between the two checks.
You can also follow this in the Windows Performance GUI and you'll see that these are live values.

---

Michael from wrote on Oct 22nd, 2012:

Just one general question about this plugin. If i check this for an adapter every 10 Minutes for example, then i'll just catch the "Network Traffic at the moment" and not the average of the last intervall?

---