Show TOC

Function documentationMetric Error Handling


The Metric Error Handling program checks whether the configuration settings, data collection and use of metrics are correct and run without errors, for metrics, managed objects or monitoring application cases such as Connection Monitoring or System Monitoring. Use this program if metrics or managed objects are gray, for example if data collection fails.

It is similar to Metric Error Handling in the context menu of metrics, in technical monitoring. The difference between them is:

  • In the Metric Error Handling program, you can select by managed object and monitoring application case, as well as individual metrics.

  • The check results are grouped by the metrics checked, and possible errors; and a detailed check log is output. The Application Log is used (see Display Log).

  • The program only finds errors, you cannot go to problem solutions, in contrast to the context menu Metric Error Handling.


Call Program

To call the Metric Troubleshooting program, call the transaction MAI_TOOLS. In the Analysis tab, choose Metrics Troubleshooting.

Specify check scope

You can specify what is to be checked. You have the following selection options:

  • Managed Object ID

    The ID of a managed object is a 32–character GUID, which is show, for example, in various log messages. You can determine the ID of a managed object in the Alerting Directory Browser. Select the managed object and a metric type, in the navigation bar. The managed object ID is output in the Metric Type Details in the Other tab.

  • Managed Object Name

    The managed object name is a technical name which is output in the monitoring interface. In System Monitoring, for example, the naming convention for ABAP instances is <system ID>~ABAP~<instance name>.

  • Technical Scenario

    To restrict the check by monitoring use cases, enter one of the following technical names in the Technical Scenario field:

    Technical Scenario

    Monitoring Use Case


    Technical System Monitoring


    Connection Monitoring


    Process Integration Monitoring


    End User Experience Monitoring


    Solution Mananger Self-Monitoring


    Business Intelligence, SBOP Monitoring


    Infrastructure Monitoring


    Interface Channel Monitoring


    Early-Watch Alert Intregration

  • Metric ID

    The ID of a metric is a 32–character GUID, which is shown, for example, in various log messages. To determine the ID of a metric, proceed as described under Managed Object ID.

  • Metric Name

    The metric name is the technical name of the metric. You can also determine it in the Alerting Directory Browser, by selecting the managed object and the metric type, in the navigation bar. This technical name is output in the Metric Type Details in the Other tab.

You specify how many metrics at the most are to be checked, in the Maximum Number of Checks field.

Display Check Results

The check log is output, by metrics; to display messages for a check, double-click on the metric in the list.

The checks are grouped for each metric into the following areas:

  • Check Data Collection

    Check whether there are any values for the metric in the Monitoring and Alerting Infrastructure, i.e. whether values have been collected.

  • Check Data Provider

    Check whether the infrastructure satisfies the prerequisites for data collection, whether, for example, the data collection agent can be reached.

  • Check Data Provider Definition

    Check whether the configuration settings collect values for this metric. Check the settings for this metric in the Alerting Directory.

  • Check Directory Configuration

    Check whether there are users for the metric (Monitoring or Reporting), and whether the metric has a valid place in the data hierarchy.

  • Check Database Metrics

    Specific checks for database metrics are displayed here.