Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
So my check_vmware_api.pl formerly check_esx3 plugin on nagios is taking VERY long variable amounts of time to monitor my esxi 6.0 host that is pretty much idle. Most of the time the plugin times out. I followed instructions online and installed other versions of Net-HTTP and libwww-perl but the issue persists.
I'm at a loss and do not know how to troubleshoot this further. I'm using VMware-vSphere-Perl-SDK-6.0.0-3561779.x86_64.tar.gz and have also tried VMware-vSphere-Perl-SDK-6.0.0-2503617.x86_64.tar.gz
How should I proceed to get this working?
Edit: I've also ran these check commands over ssh with 'time' and I get the same results. I've tried caching the session with no difference in time.
The vSphere SDKs are pretty heavy in terms of the resources required to leverage them. Are you running these checks directly from your Nagios Core machine? Can you show us the check command definitions for your VMWare checks?
You might also consider using the box293_check_vmware plugin as it's documentation is incredibly comprehensive and @box293 is a swell guy in genereal.
mcapra wrote:The vSphere SDKs are pretty heavy in terms of the resources required to leverage them. Are you running these checks directly from your Nagios Core machine? Can you show us the check command definitions for your VMWare checks?
You might also consider using the box293_check_vmware plugin as it's documentation is incredibly comprehensive and @box293 is a swell guy in genereal.
Yes the checks are running directly from the Nagios Core machine. When they are running CPU usage is almost 0, this box is nearly idle with 0.00 load.
From commands.cfg
check cpu
define service{
use generic-service
host_name testLab
#vmServer1, buildServer, backupServer
service_description ESXi CPU Load
check_command check_esx_cpu!80!90
}
# check memory usage
define service{
use generic-service
host_name testLab
service_description ESXi Memory usage
check_command check_esx_mem!80!90
}
# check net
define service{
use generic-service
host_name testLab
service_description ESXi Network usage
check_command check_esx_net!102400!204800
}
# check runtime status
define service{
use generic-service
host_name testLab
service_description ESXi Runtime status
check_command check_esx_runtime
}
# check io read
define service{
use generic-service
host_name testLab
service_description ESXi IO read
check_command check_esx_ioread!40!90
}
# check io write
define service{
use generic-service
host_name testLab
service_description ESXi IO write
check_command check_esx_iowrite!40!90
}
I sure would like to get this one working, but if i can't I'll check out the other addon. I increased my execution time on these to 300 seconds today and they are still timing out.
avandemore wrote:We don't support 3rd party plugins. If you have a slow plugin, contact the author they may be able to assist.
If you run the plugin from another system, do you get any better results?
You might have better luck having a passive check sent from VMware to the Nagios server.
That's a good stance to have, but I'm looking at nagios xi and you guys seem to offer vmware monitoring out of the box with that "To monitor VMware systems in Nagios XI is as easy as running the VMware Wizard.". What plugin are you using there?
If you run the plugin from another system, do you get any better results?
How should I run the plugin from another system? What are you suggesting?
You might have better luck having a passive check sent from VMware to the Nagios server.
Do you have any good resources you can point me to on this?
You would run the plugin from another system the same as you would from Nagios. There is nothing magical about a Nagios plugin, it's simply an executable. The executable will work from any system provided the dependencies are met.