Differences

This shows you the differences between two versions of the page.

--- blog:vcenter_vm_monitoring_with_graphite [2014/10/01 02:51] – brett
+++ blog:vcenter_vm_monitoring_with_graphite [2014/10/01 02:58] – brett
@@ Line 2: / Line 2: @@
 This was done on a CentOS 6.3 server your mileage may vary on another platform.
+The problem I was trying to solve was that I wanted to monitor the vitals of all my VM's without having to install collectd into each VM, by talking to vCenter we can pull everything out that we need.
 {{:blog:graphite-vc-tree.png?nolink|}}
-You will need to have a version of collectd compiled that has the python plugin enabled.  This can be down by downloading the collectd source and building it, making sure to have python-devel package installed.
 We don't use the collectd RPM from the EPEL repository as its too old and does not have the graphite_write plugin.
+You will need to have a version of collectd compiled that has the python plugin enabled.  This can be down by downloading the collectd source and building it, making sure to have python-devel package installed.
 Mathew has a good write on the graphite / collectd compilation and configuration for graphite.  http://blog.matthewdfuller.com/2014/06/sending-collectd-metrics-to-graphite.html
@@ Line 42: / Line 44: @@
 easy_install -U pysphere
 </code>
-This works fine in my lab where I have a single vCenter instance.
+The magic script that pulls all the stats we need.  This works in my ESX 5.1 lab where I have a single vCenter instance.
 vcenter.py