ESXi/vCenter Monitoring

[Daniel Ceola]

I did that, but it made the map a complete mess of lines that I couldn't make out.

Daniel Ceola
System Administrator
Daniel.Ceola at occfiber.com<mailto:Daniel.Ceola at occfiber.com>

From: Jim Avery [mailto:jim at jimavery.me.uk]
Sent: Monday, August 12, 2013 3:26 PM
To: nagios List
Subject: Re: [Nagios-users] ESXi/vCenter Monitoring


On 12 Aug 2013 16:50, "Daniel Ceola" <Daniel.Ceola at occfiber.com<mailto:Daniel.Ceola at occfiber.com>> wrote:
>
> Hello all,
>
>
>
> I have a lot of host servers as VM's on our ESXi infrastructure, managed with vCenter.  We also use vSphere DRS to help keep the load on host systems balanced.  Due to the DRS, our VM's can sometimes move around from being on one host to being on another w/o my knowledge beforehand.  Does anyone know if there is any sort of plugin available for Nagios Core that would basically talk to my vCenter system and find out what VM's are on which hosts, and automatically update that VM's Parent directive in the host definition?

I specify all of the host servers as parents of the VM.  I reckon that makes perfect sense, and it's dead easy to implement.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20130812/30f3ffb6/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
-------------- 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