The old format was one or more instance of usage_metering scanned the UIM domain, and created a report based on the results. Billing then read the report from usage_metering and created the billing report to be sent in to CA. With the new format there is only one instance of usage_metering which queries the database and creates the billing report based on the results.
For example with the old format, all the robots that were running one of the probes in the "Server Pack" counted as one instance so that would be 1 robot towards the count.
With the new format usage_metering counts every instance of the probe towards the total # in the overall package
Now with usage_metering 9.x, the probe measures the monitoring usage as the number of units that are monitored by the applicable monitoring probe.
The probe identifies the usage units as follows:
The usage_metering probe counts the number of resources that are monitored by the monitoring probes. The probe counts each monitored device as one resource. The probe collects information differently for local and remote probes:
For local probes, the usage_metering probe counts the host system as one resource. For example, the CDM probe monitors the CPU, disk, and memory of only the local robot system.
For remote probes, the usage_metering probe counts all the monitored hosts in the probes as different resources. For example, if you configure the net_connect probe to monitor ten resources, the usage_metering probe counts ten resources.
The usage_metering probe identifies the total capacity of storage servers that are monitored by the storage probes. For example, the probe calculates the usage of the clariion probe as the total capacity of the monitored EMC Clariion storage server (in Terabytes).