Writing Monitors for the Event Monitoring Service (December 1999)

Chapter 2 31
The EMS Application Programming Interface (API)
Functions
example, it may make sense to have a “LAN Utilization” resource that is
an RM_FLOAT64_TYPE, since it will assume values between 0.0 and 1.0.
Of course, each physical resource may be referred to by multiple logical
resources.Each logical resource that is monitored will have just one type,
however. For example, a resource monitor written to watch the physical
CPU resource may define multiple logical resources related to the CPU:
“Number of active processors” might be an RM_UBIT32_TYPE.
“CPU Utilization” might be an RM_FLOAT64_TYPE.
“CPU State” might be an RM_ENUMERATED_TYPE.
Resource monitors determine the type of a resource, and client
applications use the type specified by the resource monitor (except in the
case of an RM_ENUMERATED_TYPE, in which case the client may choose to
refer to either the state name or state value).