Build precise queries to find exactly what you need
Press ESC to close
Join our next live webinar: “Advanced Nagios Monitoring Techniques” – Register Now
Your review has been submitted and is pending approval.
This project provides techniques and solutions to use the nsca add-on to monitor a wide-area, multi-host ESX environment from a central location. Monitored resources include CPU load, memory and filesystem utilization, and VM operating states. Monitoring options are configurable to address response times and frequency of information updates.
Current Version
Last Release Date
September 17, 2011
Owner
Nagios Exchange
Compatible With
WinZip file containing documentation and scripts; password is nagios
Technical design uses the VMware command line interface (vCLI) to provide first-level Nagios monitoring and diagnosis; editable control files to specify hosts and services for monitoring; and Perl scripts that may be modified for local conditions. As of the publication date, these scripts are in production in one environment with ESX 4.0, 3.5, and 3.0; some modification may be required for other environments. Please read the documentation before attempting to install or operate the scripts. Use of these materials assumes a working knowledge of Linux and Perl, as well as VMware ESX. Documentation and scripts are supplied in a WinZip file with password nagios (lower case). If you have problems after carefully following the installation procedures, contact me by email and I will try to assist.
Hello, I am trying to setup Monitoring to my ESX hosts. I am a bit puzzled with getting it work. The thing is that I am able to run resxtop from my nagios machine and configured pl and sh files accordingly. But when it comes to configuration file I am doomed: VMware ESX hosts to monitor with Nagios nsca #Tab delimited, # in col 1 to skip schedules for 3 options #ESX Host Name Root Password CPU/Mem FileSys VMcount #------------- ---- -------- ------- ------- ------- esx-c01 root password test When I run command: root@nagios:/opt/nsca# ./nsca_vmware.pl ESX_Hosts Outcome would be: Starting execution of ./nsca_vmware.pl v1.2.1 at 2013-03-18 18:12:06 ... schedule is ESX_Hosts ./nsca_vmware.pl took 0 seconds How can I debug what went wrong? With best, Hannes
You must be logged in to submit a review.
To:
From: