VM Datastores critical

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
chrisbooth
Posts: 43
Joined: Thu Dec 01, 2016 10:09 am

VM Datastores critical

Post by chrisbooth »

I'm using the configuration wizard to monitor VMDatastores

here's the output
[[email protected] ~]$ /usr/local/nagios/libexec/check_esx3.pl -H "10.252.48.133" -f "/usr/local/nagiosxi/etc/components/vmware/ixllcisv01_IXLL_Cluster_1_auth.txt" -l "VMFS"
CHECK_ESX3.PL CRITICAL - Storages : GSWL-LargeVMs-D=1068391.00 MB (20.38%), GSWL-LargeVMs-A=1031452.00 MB (19.67%), GSWL-LargeVMs-C=960621.00 MB (20.36%), GSWL-LargeVMs-E=1120452.00 MB (21.37%), GSWL-VMs-B=971404.00 MB (61.77%), GSWL-LargeVMs-B=1039396.00 MB (19.83%), GSWL - Veeam_Backup=216752.00 MB (1.38%), GSWL-VMs-A=1011973.00 MB (64.35%), GSWL-VMs-C=1043088.00 MB (66.33%), GSWL-InstallISOs=128456.00 MB (62.80%), GSWL-Veam_Retention is not accessible | GSWL-LargeVMs-D=1068391.00MB;; GSWL-LargeVMs-A=1031452.00MB;; GSWL-LargeVMs-C=960621.00MB;; GSWL-LargeVMs-E=1120452.00MB;; GSWL-VMs-B=971404.00MB;; GSWL-LargeVMs-B=1039396.00MB;; 'GSWL - Veeam_Backup'=216752.00MB;; GSWL-VMs-A=1011973.00MB;; GSWL-VMs-C=1043088.00MB;; GSWL-InstallISOs=128456.00MB;;

as you can see it's critical but i'd like to adjust what is considered critical

but i'm having trouble finding out where to set thresholds or if the critical is passed from the vm cluster itself. if it is i can't seem to find the critical alert.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: VM Datastores critical

Post by tgriep »

I took a look at the plugin and it is not the threshold for the free space that is causing the Critical Alert it is that the GSWL-Veam_Retention datastore is not accessible and that is causing the issue..

Code: Select all

GSWL-Veam_Retention is not accessible
Does the user account used to run the plugin have enough rights to view that datastore?
You can blacklist it so it deoesn't get checked by going in to the Core Config Manager > Services, find and edit that service and add the following to $ARG3$

Code: Select all

-x GSWL-Veam_Retention
That should stop the plugin from checking that datastore.
Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
lmiltchev
Former Nagios Staff
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: VM Datastores critical

Post by lmiltchev »

According to the plugin's usage (help), you can pass warning and critical thresholds to your command.
-w, --warning=THRESHOLD
Warning threshold. See
http://nagiosplug.sourceforge.net/devel ... HOLDFORMAT
for the threshold format.
-c, --critical=THRESHOLD
Critical threshold. See
http://nagiosplug.sourceforge.net/devel ... HOLDFORMAT
for the threshold format.
Example:

Code: Select all

/usr/local/nagios/libexec/check_esx3.pl -H "10.252.48.133" -f "/usr/local/nagiosxi/etc/components/vmware/ixllcisv01_IXLL_Cluster_1_auth.txt" -l "VMFS" -w <value> -c <value>
Keep in mind that even if one of the datasores is above the warning or critical values, the check will change to "non-ok" state. You can create different checks for different datastores if you wish by passing a subcommand (-s).

Example:

Code: Select all

/usr/local/nagios/libexec/check_esx3.pl -H "10.252.48.133" -f "/usr/local/nagiosxi/etc/components/vmware/ixllcisv01_IXLL_Cluster_1_auth.txt" -l "VMFS" -s GSWL-LargeVMs-D -w <value> -c <value>
or

Code: Select all

/usr/local/nagios/libexec/check_esx3.pl -H "10.252.48.133" -f "/usr/local/nagiosxi/etc/components/vmware/ixllcisv01_IXLL_Cluster_1_auth.txt" -l "VMFS" -s GSWL-LargeVMs-A -w <value> -c <value>

Hope this helps.
Be sure to check out our Knowledgebase for helpful articles and solutions!
chrisbooth
Posts: 43
Joined: Thu Dec 01, 2016 10:09 am

Re: VM Datastores critical

Post by chrisbooth »

great thank you
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: VM Datastores critical

Post by dwhitfield »

It sounds like this issue has been resolved. Is it okay if we lock this thread? Thanks for choosing the Nagios forums!
Locked