VMWare monitoring agent for Nagios and MRTG

[Steve Shipway]

So, I¡¯m working on an agent to link VMware to both Nagios and MRTG.

 

This is intended to allow us to get alarms from VMware into Nagios,
including alerts on things like disk latency and CPU ready time; also to get
graphs in MRTG for the main VC metrics without having to load up the whole
VC client.  The graphs also show percentages of configured maxima and split,
which is easier to understand than the VC Client graphs.

 

It is currently working in beta.  The features are ¨C

¡¤         Runs as a daemon, polling every 5min (configurable)

¡¤         Talks to the VirtualCentre to collect data on the entire
datacentre

¡¤         Outputs to MRTG (via rrdcached) and Nagios (via livestatus) (can
disable either).  Services in Nagios are configured as passive, with a
freshness check to alert if the agent dies; in MRTG, data is pushed directly
into the RRD, so MRTG never runs, only the RRD frontend (eg, Routers2).

¡¤         Support for duplicate (DR) livestatus server to receive copies of
status updates

¡¤         Configurable thresholds for all metrics

¡¤         Can create config files for both MRTG and Nagios dynamically, so
as your farm structure changes, so does the monitoring.  Config files are
optimised for Routers2/RRD/MRTG setup.

¡¤         Can validate guest identities via hostname, DNS, livestatus, etc

¡¤         Logging to file, syslog, Nagios

¡¤         Collects stats on disk use (traffic and latency per vdisk),
network use (traffic per interface), CPU (including split) and memory
(including split)

¡¤         Collects info on Datastore usage, cluster balance, Virtualcentre
alarms, guest up/down

¡¤         Config files generated by TT2 templates, so you can modify them
as required

¡¤         Tested with VC holding 4 datacentres, 17 clusters, 51 hosts, 1300
guests with MRTG and Nagios, and it takes 5min to complete poll

 

Is anyone interested in giving it a try, given that there is very sparse
documentation for it as yet?  If so, please contact me direct.

 

This is the fully-rewritten child of the old check_vmware.pl plugin for
Nagios/MRTG that I wrote, which was itself the child of check_esx3.

 

Steve

 

Routers2/MRTG/RRD graph for CPU

hosts-maillstappprd01.its.cfg-_lstappprd01.its.auckland.ac.nz-cpu-combined-d
-x3.png

 

  _____  

Steve Shipway

ITS Unix Services Design Lead

University of Auckland, New Zealand

Floor 1, 58 Symonds Street, Auckland

Phone: +64 (0)9 3737599 ext 86487

DDI: +64 (0)9 923 6487

Mobile: +64 (0)21 753 189

Email:  <mailto:s.shipway at auckland.ac.nz> s.shipway at auckland.ac.nz

P Please consider the environment before printing this e-mail : ´òÓ¡±¾Óʼþ£¬
½«¼õÉÙÒ»¿ÃÊ÷´æ»îµÄ»ú»á

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20130605/6a7b3a92/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 69886 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20130605/6a7b3a92/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5900 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20130605/6a7b3a92/attachment.bin>
-------------- next part --------------
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null