Diagnosing metric promotion issues

Unlike other targets, the performance and usage metrics for a service target, as described before, are not collected directly by agents. Instead, they are computed within the OMS repository based on the metrics for either the system components or the service tests. As the promoted metrics are collected as repository metrics, debugging and diagnosing any issues in the service metric collection is not straightforward. OEM Grid Control provides two options to do the diagnostics, manual and through command-line scripts.

Manual diagnostics

In this case, the system administrator needs to check if all the underlying metrics are collected properly and if the repository metric collection job is executed without errors. A promoted service metric can show No Data due to a variety of reasons such as configuration errors, that is, a dependent system component being deleted, beacon test disabled, due to repository job errors, and so on. The following steps are to be performed...