The Usage Metering (usage_metering) probe identifies the resources and the total capacity of your monitored environment. The probe then generates the following types of billing reports:
Note: The probe is available only through the Infrastructure Manager interface.
Important! From version 9.00, the usage_metering probe does not require the billing probe to generate the reports. For information about the earlier version, see usage_metering Version 8.0.
The usage_metering 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:
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).
Different versions of the probe support distributed usage calculation, as follows:
|From usage_metering 9.00||The probe generates an overall summary report and individual billing reports for each origin (CA UIM hub) in your CA UIM environment. CA recommends you to upgrade to the latest version of the probe.||Managed Service Providers (MSPs) and on-premise enterprise customers with distributed environments can use the origin-specific reports.|
|Until usage_metering 8.00||You can deploy multiple instances of the usage_metering probe. The primary instance resides on the primary hub. You can deploy secondary instances on other hubs. For information about the earlier version, see usage_metering Version 8.0.||Managed Service Providers (MSPs) and on-premise enterprise customers with distributed environments can deploy instances on robots of all hubs for localized reports.|
Some probe configurations contain device references that do not map to a specific IP device.
For example, with database server clustering, the cluster manager resolves the instance name to a server location at connection time. The oracle probe refers the TNS alias that is defined by the Oracle client and resolves the alias to the specific server device.
The usage_metering probe replaces virtual device references with the actual Fully Qualified Domain Names (FQDN) and IP addresses. The probe ensures that the billing summary reports include the correct number of devices, and not the number of systems in the cluster.
You can export an HTML billable items report containing summary and detail information after usage calculation completes. You can then open the report in any Web browser or spreadsheet application for advanced features such as filters and pivot tables, as required. CA Sales Operations require you to generate and send your billing reports each month.
Note: In previous versions of the probe, where usage_metering required the billing probe to generate reports, the billing report was generated weekly. With the new version of the probe, the reports are generated monthly.
Important! From usage_metering version 9.01, you can use the webgtw probe to automatically upload the overall summary report to CA support.