I have written previously about the vCloud Ecosystem (part1) (part2), which combines multiple products to make up a vCloud environment. What I want to cover in this article is VMware vC Ops and VMware vFrabic Hyperic integration into this ecosystem product stack. Where do these products fit in?
When we look at vC Ops and Hyperic, we need to look at two different aspects of monitoring. Availability and Performance. vC Ops gives us the ability to gather performance data, while Hyperic is used to provide application availability.
So how do they integrate?
The above diagram demonstrates the different integration points between the vCloud stack. This can be further expanded upon to also include availability monitoring of the other vCloud components, however this can also be achieved simply by having all these vCloud Management VMs running in a Management Cluster vCenter as per the vCloud Architecture Toolkit and using a vCenter adapter to monitor there availability.
As demonstrated in the diagram all the vCloud infrastructure components are monitored either through vFabric Hyperic relaying information to vC Ops, or through vC Ops adapters themselves.
Through the vC Ops vCenter adapters this allows us to monitor the virtual machine status of all cloud workloads. We can determine if these are up or down, however no information regarding the actual state of the application workloads running in these virtual machines can be monitored.
In the future I will be able to provide information around what application specifics within vCloud Director and Chargeback we can use to monitor actual availability.