WMI plus checknetworks on all adapters

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
CFT6Server
Posts: 506
Joined: Wed Apr 15, 2015 4:21 pm

WMI plus checknetworks on all adapters

Post by CFT6Server »

Is there a way to grab the network stats of all network adapters without having to specify the name when using Check_WMI_plus's checknetwork? it asks for the -a 'adapter name' arguement, but perhaps it can be like checkdiskio where I can do a wildcard? Otherwise, any suggestions on how to mass deploy this check to all servers without having to know what the adapter names are?
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: WMI plus checknetworks on all adapters

Post by hsmith »

I'll reach out to the developers and see if there is a way to do this. It seems like that could be something useful for the wizard to detect.
Former Nagios Employee.
me.
CFT6Server
Posts: 506
Joined: Wed Apr 15, 2015 4:21 pm

Re: WMI plus checknetworks on all adapters

Post by CFT6Server »

Thanks and yes this would be awesome to add to the WMI wizard as well.
CFT6Server
Posts: 506
Joined: Wed Apr 15, 2015 4:21 pm

Re: WMI plus checknetworks on all adapters

Post by CFT6Server »

I do have one more questiosn re: WMI checks for network. Is there a switch for units of measurement? Since it is bytes per sec, whether it is KB/MB/GB, was wonder if we can set the Y-axis to say MB.
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: WMI plus checknetworks on all adapters

Post by hsmith »

The developer who has done a majority of our WMI stuff is out of the office sick right now. I'm going to reach out to the other developers, I hadn't realized he was out sick. My apologies for the delay. I assume this is also Check_WMI_plus's checknetwork?
Former Nagios Employee.
me.
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: WMI plus checknetworks on all adapters

Post by hsmith »

Apparently this is a thing from the man page. Is this what you're looking for here?

Code: Select all

checknetwork  
   These network checks use WMI Raw counters to calculate values over a given timeperiod. 
   This is much more accurate than taking Formatted WMI values.
   ARG1  Specify the network interface the stats are collected for.  If set to . all interfaces will be included.
      To include multiple interfaces separate them with a | or specify a common identifier eg part of an IP Address or MAC Address. This uses a regular expression so take care to
      specify exactly what you want. eg "LAN0" or "192.168.0.1" or "192.168.0" or "LAN0|LAN2" or "." or "08:00:27:85:CE:6D" or "08:00:27"
      To specify a network interface you can use either the Connection Name (as seen in Control Panel), IP Address (IPv4 or IPV6) or MAC Address. You can also use the name of the network adaptors as seen from WMI which is similar to what is seen in the output of the ipconfig/all command on Windows. However, it is not exactly the same and can be tricky since this uses a regular expression. Run without -a to show the interface
      names, IP Addresses, MAC Addresses. Typically you need to use '' around the adapter name when specifying.
   DELAY  (optional) specifies the number of seconds over which the utilisation is calculated. The longer you can make this without timing out, the more accurate it will be. If specifying longer values. You may also need to use the -t parameter to set a longer script timeout. Only valid if also specifying --nokeepstate ie you are not using the state keeping feature. We recommend that you do keep state and hence do not use --nokeepstate.
   WARN/CRIT  can be used as described below.
      Valid Warning/Critical Fields are: CurrentBandwidth (Default), _PacketsSentPersec, _PacketsReceivedPersec, OutputQueueLength, PacketsReceivedErrors, _BytesSentPersec, _BytesReceivedPersec, _SendBytesUtilisation, _ReceiveBytesUtilisation
   BYTEFACTOR  defaults to 1000 for this mode. You can override this if you wish.

   Note:  
      This check does up to 3 WMI queries so it may be slow. You might need to use the -t option. Since 2 of the WMI queries are relatively static, their results are cached and you can set the refresh period for this data using --joinexpiry.
Former Nagios Employee.
me.
Locked