How to Monitor vCloud Director Using eG Enterprise?
eG Enterprise can monitor a vCloud Director cell in an agent-based or an agentless manner. To monitor the cell in an agentless manner, you need to deploy an eG agent on a remote Windows host in the environment and configure that remote agent to run using domain administrator privileges.
Regardless of the monitoring approach used (agent-based or agentless), the eG agent uses the vCloud API to run the tests mapped to the top-4 layers of the monitoring model (see Figure 1) and report a variety of metrics - these include availability metrics, status indicators, measures exploring the resource allocation to and resource usage of pvDCs and org vDCs, and more. On the contrary, the eG agent uses the REST API instead of vCloud API to collect metrics when the cell in the vCloud Director 10.0 is to be monitored. To ensure access to the vCloud API and REST API (in case, if you are monitoring the cell in the vCloud Director server 10.0), the tests mapped to the top 4 layers need to be configured with the credentials of a user who has Administrator access to the vCloud Director cell to be monitored.
On the other hand, the fifth layer of Figure 1- i.e., the vCloud Internals layer - uses JMX to pull out metrics of interest from the cell regardless of the vCloud Director version. To make sure that the tests mapped to the vCloud Internals layer work, you need to enable JMX for the vCloud Director cell to be monitored. By default, JMX requires no authentication or security (SSL). In this case therefore, to use JMX for pulling out metrics from vCloud Director cell, a set of pre-requisites should be fulfilled. These requirements have been discussed in the Pre-requisites for Monitoring vCloud Director.