Reporting usage metrics with IBM Usage Metering Service

It is your responsibility to maintain compliance with the licensing terms and conditions. However, to audit the use of IBM software, UMS is used to capture business value metrics and send, automatically and periodically, compliance data for auditing purposes to SWC.

To disable UMS, when it is enabled

1. Update the Business Automation Insights CR by setting shared_configuration.sc_enable_usage_metering to "false".
2. When the change is complete, the Business Automation Insights operator picks up the change in the next reconcile and sets the enable flag in the connection point (kind:IBMUsageMetering) to false.
3. The operator also deletes the cron job that is defined to send metrics to SWC.

To enable UMS, when it is disabled

1. Update the Business Automation Insights CR by setting shared_configuration.sc_enable_usage_metering to "true".
2. When the change is complete, the Business Automation Insights operator picks up the change in the next reconcile and sets the enable flag in the connection point (kind:IBMUsageMetering) to true.
3. The operator starts the cron job that is defined to send metrics to SWC.

By default, usage metering is enabled and Business Automation Insights sends usage metrics data to UMS daily.

A single payload is used to send multiple metrics that are correlated for each capability. Data from local storage can be obtained through REST API as a snapshot file or a JSON object. It can then be used for local dashboarding or sent to reporting tools, such as IBM License Service Reporter (LSR).

Business Automation Insights uses the following identifiers. The identifier or productId is used to correlate data based on whether it is a non-production or production deployment license type.

The following metrics are collected in addition to values for the version, environment, architecture, and platform.

• Storage usage.
• Number of events per capability.
• Number of monitoring sources.
• Number of dashboards.
• Number of charts per dashboard.
• Average event size.