ESXi/vCenter Monitoring

[Chris Beattie]

On 8/12/2013 4:04 PM, Daniel Ceola wrote:> I did that, but it made the map a complete mess of lines that I couldn't
> make out.

Try check_cluster.  Check_cluster aggregates the status of individual ESX hosts.  The clusters here have three or four ESX hosts each.  If one ESX host in the cluster is offline, my check_cluster returns a warning.  If all but one are offline, I have it return a critical.  At that point, the engineers have more important things to worry about than individual guests.

I have a fake "host" for each cluster whose check_host_alive is the check_cluster command.  The guest VMs on each cluster have the fake host set as their parent.  The guests can move around all they want and I don't have to change anything.

When the engineers change the clusters by adding or removing ESX hosts, all I have to do is add or remove one ESX host check and update the check_cluster command.  I don't have to edit the list of parents for all the guest VMs, which is important, because we have more than a thousand of them.

--
-Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20130812/3171404a/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