You can view the health status of your vRealize Hyperic agents, including the number of platforms an agent monitors, the number of resource metrics that an agent collects, and the number of licenses consumed by an agent.

You view the status of all agent that are registered with the vRealize Hyperic server on the Agents tab of the HQ Health page.

Health Data for an Agent

The data that you can view is described in the following table.

Table 1. Agent Health Data

Field

Description

Notes

FQDN

Fully-qualified domain name of the platform where the agent runs.

Address

IP address of the platform where the agent runs.

Port

Port where the agent listens for communication with the vRealize Hyperic server.

If you configure unidirectional agent - server communications, the agent initiates all communications with the vRealize Hyperic server.

Version

Agent version number.

Although an agent might work successfully with an vRealize Hyperic server of a later version, it is strongly recommended that you run the same version of the agent and server.

Build #

Agent build number.

Bundle Version

Agent bundle version.

Creation Time

The date/time that the vRealize Hyperic agent was first started up.

# Platforms

Number of platforms the agent manages.

Typically, an agent manages one platform - the platform where it runs. Exceptions include:

  • If the agent manages a vSphere vCenter instance, the number of platforms shown is the number of virtual machines the vCenter server manages.

  • If the agent manages remote network devices or network host platform types.

# Metrics

The number of resource metrics the agent collects. This is the total number of metrics that are configured for collection across all resources the agent monitors.

If one agent bears an inordinate metric load, you might be able to distribute it more evenly.

Time Offset (ms)

The difference in system clock time between the agent and the vRealize Hyperic server.

A time offset can cause incorrect availability reporting.

License Count

The number of platform licenses consumed by the agent.

Typically, a single agent consumes a single license.

If an agent manages a vCenter vSphere instance, it consumes a license for the platform that hosts vCenter, a license for each vSphere vHost administered by the vCenter instance, and, if an agent is installed in each virtual machine, license for each vSphere virtual machine on each vHost.