This topic details all of the supported platform types in vCenter Hyperic.

The table below lists all supported platform service types in Hyperic. The Configuration Notes column for a network service or another platform service type that require configuration has a link to a configuration properties reference for the service type. No configuration instructions are provided for auto-discovered platform services.

Configuration Instructions for Platform Services



Configuration Notes


The Hyperic Agent on a platform automatically discovers CPUs on the platform.

It is not necessary to manually configure CPU monitoring. For information about metrics available for a CPU, see CPU Service.


Use to monitor a remote Dynamic Host Configuration Protocol server.

See Configure the DHCP Service.


Use to monitor a remote Domain Name System server.

See Configure a DNS Service in vCenter Hyperic.

FileServer Directory

Use to monitor a directory.

See FileServer Directory Service.

FileServer File

Use to monitor a file.

See FileServer File Service.

FileServer Mount

Use to monitor a filesystem mount point and associated disks and raid arrays.


The Hyperic agent auto-discovers local mount points. You only need to explicitly configure a FileServer Mount service to monitor a remote network file system (NFS). Alternatively, you can install a Hyperic agent on the system that hosts the NFS, in which case the NFS will be auto-discovered.

See FileServer Mount Service.

FileServer Directory Tree

Use to monitor a directory and the entire tree under that directory.

See FileServer Directory Tree Service.


Use to monitor a particular URL.

See Configure the HTTP Service.


Use to monitor a remote File Transfer Protocol server.

See Configure the FTP Service.


Use to monitor a remote Internet Message Access Protocol server.

See Configure the IMAP Service.

InetAddress Ping

Use to ping a remote host for availability.

See Configure the InetAddress Ping Service.


Use to monitor a remote Lightweight Directory Access Server.

See Configure the LDAP Service.


Use to monitor multiple related processes. For example, to monitor the number of httpd processes running on Apache and the system resource they consume in aggregate.

See Multiprocess Service.

NetworkServer Interface

Use to monitor a network interface.


Because the Hyperic agent auto-discovers network interfaces, manual configuration of a NetworkServer Interface is rare.

See NetworkService Interface Service.


Use to monitor a remote Network Time Protocol server.

See Configure the NTP Service.


Use to monitor a remote Post Office Protocol 3 server. Configure along with an SMTP service to monitor incoming and outgoing email services.

See Configure the POP3 Service.


Use to monitor a process using a Hyperic SIGAR Process Table Query Language (PTQL) query. To configure, you supply the PTQL query in the form:


For example:


See Process Service.


Use to monitor a Remote Procedure Call service.


Not available on Windows platforms.

See Configure the RPC Service.


Used to configure Hyperic to periodically run a script that collects a system or application metric.

See Script Service .


Use to monitor a remote Simple Mail Transfer Protocol server. Configure along with a POP3 service to monitor incoming and outgoing email services.

See Configure the SMTP Service.


Use to monitor a remote Simple Network Management Protocol agent.

See Configure the SNMP Service.


Use to monitor a remote SSH service.

See Configure the SSH Service.

TCP Socket

Use to monitor the availability of a remote TCP socket

See Configure the TCP Socket Service.

Windows Service

Use to monitor an application that runs as a service under Windows.

To configure it, you supply its Service Name in Windows. To determine the Service Name:


Click the Windows start menu and select Run.


Type services.msc in the run dialog and click Ok.


In the list of services displayed, right-click the service you wish to monitor and select Properties.


Locate the Service Name on the General tab. See Windows Service.