Show TOC

Function documentationUsing the Metric, Event and Alert Details Program


The tool to show metric, events and alert details is an expert tool for finding and analyzing errors within the end-to-end Monitoring and Alerting Infrastructure of SAP Solution Manager. Use it to display a great deal of technical information and the status of metric types and managed objects. On the selection screen of the program, you can specify the managed objects and metric types and the data about these objects that you want to display.

The information displayed is similar to that displayed in the Alerting Directory Browser, however in this case, the data is called in the SAP GUI, which is significantly easier, particularly if the system's availability over HTTP is limited. The results are also displayed in a continuous list. This means that, although the display is not as clear as in the Alerting Directory Browser, you can search the entire output for any character strings, for example, for IDs from a log entry or an error message.

This is the way in which you usually use the program. When finding and analyzing errors, you often start from an error message that contains the area in which the error occurred and the ID of the affected metric or managed object. You can enter both of these pieces of information on the selection screen of the program. To find the related information that is relevant for you when identifying the error, search the program's output list for this ID.


Call Program

There are two ways of calling the Metric, Event and Alert Details program:

  • Start transaction MEASCOUT.

  • Start transaction MAI_TOOLS. In the Analysis tab, choose Metric, Event and Alert Details.

Define the Desired Scope

You can select which data is displayed. You have the following options:

  • In the Metric Type Selection group box, you can determine the managed objects or metric types about which you want to display information. You have the following selection options:



    Entry Point

    There is a hierarchy of MOs for each monitoring use case (which can actually only consist of a single level). The entry point is the top hierarchy level for these MOs.

    Example Example

    The entry point for the application case System Monitoring is technical system, and the MO types technical instance, host, and database are below it in the MO hierarchy.

    End of the example.

    Monitoring Use Case

    The end-to-end Monitoring and Alerting Infrastructure (MAI) provides different monitoring use cases for different monitoring areas. For example, System Monitoring, Self-Monitoring, or End-user Experience Monitoring.

    IDs of managed objects

    Each MO has a 32 character GUID, which is its ID. This ID is, for example, output in logs and error messages. In the Alerting Directory Browser, this ID is displayed at metric level on the Other tab page.

    Names of managed objects

    A managed object (MO) is an object in your system landscape or business process landscape. All metrics, events, or alerts are assigned to an MO. The name of the MO is a technical name, which follows a particular naming convention depending on the MO type.

    Example Example

    For a technical system, the MO name is [System-ID]~[Systemtyp]

    For a technical instance, the MO name is [System-ID]~[Systemtyp]~[Instanzname]

    End of the example.

    Types of managed objects

    There are different types of MOs, depending on the monitoring use case.

    Example Example

    The MO types in System Monitoring are technical system, hosts, technical instances, databases, and technical scenarios.

    End of the example.

    Metric type IDs

    Each metric type has a 32 character GUID, which is its ID. This ID is, for example, output in logs and error messages. In the Alerting Directory Browser, this ID is displayed on the Other tab page.


    You can restrict the displayed data to a specified variant. The Variant is a key field for the objects in technical monitoring. The UIs only display objects with the variant Active. The variants Inactive and Test are used by developers to test monitoring enhancements, without yet influencing the infrastructure functions or display. You should not need to change the default value Active.

  • In the group box MEA Repository, you can set the Display Assigned Templates flag. Several templates can be assigned to one managed object, but only one template can be used for one managed object in a product (see below). You can display and change both assignments in the SAP Solution Manager Configuration (transaction SOLMAN_SETUP).

  • In the MEA Directory group box, you can specify which data from the alerting directory is displayed for the MOs or metric types selected above. You have the following options:



    Display Global Work Mode

    The assigned work modes are displayed here, broken down by the monitoring use cases. The program also displays whether the data for the relevant work mode is used for monitoring and/or reporting.

    Note Note

    This information is not dependent on the selected MO.

    End of the note.

    Show Entry Points

    For the selected MO, the entry point for each monitoring application that the MO is assigned to is displayed, along with the IDs of that entry point.

    Display applied templates

    The metrics and their properties are stored in templates; these templates are, in turn, assigned to monitoring use cases and product versions. The templates to which the MO is assigned are displayed.

    Display context names

    Landscape attributes are assigned to each MO, depending on the monitoring use case. For each monitoring use case there is a set of landscape attributes that are filled for the MO at the time of configuration. There is therefore a set of variable names and values for the MO. These are displayed here.

    Display product IDs

    One or more product versions are assigned to each MO (depending on the monitoring use case). These are displayed here.

    Display event hierarchy

    An event must be part of an event hierarchy. The event must be assigned to one of the valid categories (Availability, Configuration, Performance, or Exception) and to the MO itself or to one of the associated lower-level MOs. All event types from the event hierarchy that are assigned to the selected MO are displayed here.

    Show Metric Definition

    The most important technical information for the metrics is displayed, as in the Alerting Directory Browser. This includes the following information:

    • The MEA Consumer specifies which application uses the values of this metric. Possible applications are Alerting and Reporting. This setting depends on the work mode.

    • The Rule Type determines how the severity of a metric type and event type are determined from the measured values.

    • Collector Paramters contain technical information about details of the data collection, primarily parameters and their values that the data collector requires. In the Alerting Directory Browser, this information is displayed on the Data Collection tab page.

    • The Collector Type specifies the technical realization to get the measured values of metrics. The most important collector types include PULL_RFC, in which the Extraktor Framework regularly queries the values of the managed object via an RFC connection, and PUSH_GENERIC, in which an agent passes the data to the SAP Solution Manager system.

    Display Event Definition

    Display Alert Definition

    You can also display the technical data of the event and alert types in the alerting directory for the managed objects to be displayed.

  • In the Data Provider Connector group box, you can specify whether you want to display the assigned agents for the selected MOs. As well as the name of the agent, the system displays whether data collection is active for the agent in the Data Collection column.

  • In the Event Calculation Engine (ECE) group box, you can set the following flags to display the associated information:



    Display metric store overview

    You can display here whether there are any values in the MAI for the metric types that are assigned to the managed object. If the corresponding status is red, there are no values for the metric type in the metric store. If there are values, the last measured value is displayed.

    Note Note

    A green status does not necessarily mean that the associated metric value has already been evaluated by the Event Calculation Engine. It is therefore possible that associated events or alerts have not yet been created. A green status does not exclude the possibility that the associated metric has the status gray (value is obsolete) in the MAI. Although the metric store is regularly reorganized, obsolete values can remain in the metric store for a time.

    End of the note.

    All Values in Metric Repository

    You can display all measured values in the metric repository for the selected managed object.

    Aggregation per Selected MO

    You can also display the values which the ECE has calculated for the selected object.

  • In the BI Evaluations group box, you can select Display BI metric log to display whether values have been transferred to BI for the selected metric types. If this is the case, periods and technical data for this transfer is displayed.

Display the Desired Information

Once you have specified which information you want to display for which managed objects or metric types, choose the (Execute) button. The requested information is displayed as a list.

The list contains links to the following two tools, at metric level: