View Status of all Hyperic Agents

Topics marked with * relate to features available only in vFabric Hyperic.

The page has information about the Agents tab of the HQ Health page — a screenshot, and definitions of the health data for an agent.

For information about using HQ Health to troubleshoot problems, see Troubleshoot Agent and Server Problems.

Agents Tab in HQ Health

The Agents tab of the HQ Health page — shown in the screenshot below — shows the status of all of the Hyperic Agents that are registered with the Hyperic Server.

To navigate to HQ Health, click the link for it in the Plugins section of the Administration page.


Health Data for an Agent

The table below defines the information on the Agents tab of HQ Health,





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



IP address of the platform where the agent runs.



Port where the agent listens for communication with the Hyperic Server.

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


Agent version number.

Although an agent might work successfully with an 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 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 VMs 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 may be able to distribute it more evenly. See the "Overloaded Agent" section of Troubleshoot Agent and Server Problems.

Time Offset (ms)

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

A time offset can cause incorrect availability reporting. See the "Out-of-Sync Agent and Server Clocks" section of Troubleshoot Agent and Server Problems.

A question mark in this column indicates that the Hyperic Server is unable to contact the agent. True?

License Count

The number of platform licenses consumed by the agent.

Typically, a single agent consumes a single license.

If an agent manages a vSphere vCenter 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 VM --- a license for each vSphere VM on each vHost.