VMware replace default graphing
Description
Acceptance / Success Criteria
Lucidchart Diagrams
Activity
Seth Leger October 21, 2015 at 6:07 PM
I believe that this fix was merged into 1.12. Marking as fixed.
Ronny Trommer June 12, 2014 at 8:09 AMEdited
Backported to origin/1.12 with commit 9302d5f5f3c143a9f0eaa0fde463ff8126ae9f77
Ronny Trommer May 26, 2014 at 6:48 AM
merged to master with commit: 9433d90739a71c7d16a1f6a03bdeeefb16e18f0b
Alejandro Galue February 24, 2014 at 1:17 PM
I agree. Actually it doesn't make sense and the customers can't see the benefit of the VMWare Integration without those graph templates, specially because they can obtain nicer graphs having SNMP graphs on the VMs (which is the typical case). So, the templates for CIM and ESX are even more important than the templates for the VMs (but that doesn't mean we should forget about the graphs for the VMs).
Jeff Gehlbach February 24, 2014 at 1:07 PM
Let's get this merged – it's 100% giant win compared to the default VMware5 graph stuff. We can stuff the old vmware5-graph-simple.properties into etc/examples or something for people who want to see the old, ugly presentation of every obscure metric that's not included in this new set.
Details
Details
Assignee
Reporter
Labels
Fix versions
Affects versions
Priority
MajorPagerDuty
PagerDuty Incident
PagerDuty
With the VMware integration it is possible to collect metrics provided by vCenter about Host-Systems and virtual machines. The graphs are currently automatic generated as single line graphs and don't have any unit or human readable meaning. To make the datacollection from VMware metrics useful the graphs should be refactored using the VMware documentation[1] to represent the metrics correctly.
[1] https://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.wssdk.apiref.doc/memory_counters.html
Working branch: origin/vmware-graph-improvement