Specifying thresholds hasn't been added to the vmware wizard, because it would be a very complicated task. The check_esx3.pl uses many "subcommands" for various metrics. Setting a warning or a critical threshold wouldn't make any sense unless you specify a "subcommand". I will give you a simple example. From the plugins usage:
Host specific :
* cpu - shows cpu info
+ usage - CPU usage in percentage
o quickstats - switch for query either PerfCounter values or Runtime info
+ usagemhz - CPU usage in MHz
o quickstats - switch for query either PerfCounter values or Runtime info
^ all cpu info
As you can see, if you don't use a subcommand (usage or usagemhz), you would be monitoring both metrics. Specifying thresholds in this case won't be very useful.
Examples:
Here, the plugin returns OK state, as the usage is below the warning and critical thresholds.
Code: Select all
/usr/local/nagios/libexec/check_esx3.pl -H "x.x.x.x" -f "/usr/local/nagiosxi/etc/components/vmware/VVMWARE_HOST_auth.txt" -l "CPU" -s usage -w 40 -c 50
CHECK_ESX3.PL OK - cpu usage=32.24 % | cpu_usage=32.24%;40;50
The same thresholds return CRITICAL, when you monitor the CPU usage in MHz.
Code: Select all
/usr/local/nagios/libexec/check_esx3.pl -H "192.168.7.20" -f "/usr/local/nagiosxi/etc/components/vmware/VVMWARE_HOST_auth.txt" -l "CPU" -s usagemhz -w 40 -c 50
CHECK_ESX3.PL CRITICAL - cpu usagemhz=13588.00 MHz | cpu_usagemhz=13588.00MHz;40;50
If you didn't specify a "subcommand" though, the return code would be OK.
With some checks, you monitor several metrics at the same time but you may be interested in only monitoring one or two of them. Each one would require different warning and critical thresholds...
There isn't any good way, as far as I know, to add thresholds in bulk to many checks with one go. You will have to do this manually in the CCM.
Note: Initially, I was thinking of using the Bulk Modifications Tool, in which you can change arguments for hosts and services. However, you cannot
append arguments. If you don't include the existing args (leave the fields blank), they will be wiped out. In order to find out what your existing args are, you will need to log in the CCM, and review your service config. Once, you long in the CCM, you might as well modify the args there... I hope this makes sense.