Show TOC

Function documentationDetermining CCMS Metric Attributes


Note Note

This section is the first part of the Extend Monitoring and Alerting Infrastructure with CCMS Metrics process. This process shows how you can extend technical monitoring with additional, previously not monitored CCMS metrics.

End of the note.

To integrate CCMS metrics from the Alert Monitor, which are not displayed in technical monitoring by default, into the Monitoring and Alerting Infrastructure (MAI), you need various attributes of the CCMS metrics, which you can get from the Alert Monitor (transaction RZ20).

The section describes which attributes these are, and how you can get them. The attributes are the following:

  • MTE class

    The MTE class combines semantically identical Monitoring Tree Elements (MTE), and is roughly equivalent to the technical name of a metric in MAI. The name of the MTE class is independent of the name of the technical system or instance of the metric. An example is R3DialogResponseTime, the mean dialog response time of an ABAP instance.

  • Object Name

    A monitor object groups metrics thematically in CCMS, e.g. the CPU of a server, the dialog system or background processing. The monitor object also groupps graphically within a monitor tree, in the Alert Monitor, where it is shown by the symbol . The MTE class usually characterizes an MTE uniquely within a context, for example within an instance (in which case you do not need the object name). You only need the object name if there are several MTEs with the same MTE class in a context.

    Example Example

    The MTE class of the update response time R3UpdateResponseTime does not uniquely identify an MTE within an instance, because there are two update modules, V1 and V2, which are modelled by two monitoring objects PerformanceU1 and PerformanceU2. Only the combination of object name and MTE class specify this MTE uniquely.

    End of the example.
  • Context name

    The context is roughly a container for MTEs in CCMS; for instance-specific MTEs, the context is the technical instance; for system-specific MTEs, the context is typically a monitoring subject area.

  • MTE Type

    Depending on the CCMS metric type which you want to monitor in MAI, you may have to use different collectors. The icon displayed identifies the type of an MTE in the Alert Monitor. There are five monitor attribute types:



    Performance Attribute

    collects reported numerical performance values, and calculates their mean

    Status attribute

    reports error message texts and alert status

    Heartbeat Attribute

    checks whether SAP system components are active; if no values are reported for a long time for a monitor attribute, it raises an alert

    Log attribute

    checks log and trace files (these attributes can use an existing log mechanism, for example the SAP system log, or be used by an application to implement its own log)

    Text attribute

    contains information with no alert rating; the text can be updated as required

  • Granularity

    The granularity states how often the CCMS metric is measure, the resolution of the metric. This attribute is relevant above all for performance.

  • Instance-specific or system-wide

    You use different collectors for integration into technical monitoring, depending on whether the CCMS metric is instance-specific or system-wide.


You can get these attributes for an MTE to be monitored in MAI, in two steps:

  1. Localize the CCMS metric in the alert monitor.

  2. Get the attributes of the MTEs in the Alert Monitor.

Localize the CCMS metric in the alert monitor.

You can ignore this section for a CCMS metric to be monitored in technical monitoring , if you can already navigate to it in a monitor. It is also possible that you only know the MTE class of the metric. In this case, proceed as follows:

  1. Start the Alert Monitor with the transaction code RZ20.

  2. In the monitor collection SAP CCMS Technical Expert Monitors, start the monitor All Monitoring Contexts. This monitor contains all CCMS metrics in a system.

  3. In the Start of the navigation path Views menu, choose Next navigation step MTE Info End of the navigation path. This view also shows the class of the MTEs displayed.

  4. Expand the monitor by selecting the root node All Monitoring Contexts and choosing Expand Tree (F6).

  5. Locate the MTE class by choosing (Find), and entering the name of the MTE class, in the Find screen, iin the field Search for. Choose (Find) again.

  6. MTE class hits are displayed. The contexts in which the MTE class is found indicate whether the metric is determined per instance or system-wide.

Get the attributes of the MTEs in the Alert Monitor
  1. You are in the Alert Monitor, and have found the MTE.

  2. The icon in front of the MTE name indicates the type of the MTE.

  3. Select the MTE and choose Attributes. The Monitoring: Attributes and Methods screen is displayed for the MTE.

  4. The full MTE name is displayed at the top of the screen , in the field Attributes ofn. Thie name has the following structure:

    <system ID> \ <context name> \ <path element> \ <object name> \ <attribute name>

    Example Example

    The full name can have the following value for the dialog response time:






    <system ID>


    MTE system ID

    <context name>


    In this case, the context name is the instance name, so the metric is determined at instance level.

    <path element>

    R3 Services

    There can be none or several path elements, depending on the modelling

    <object name>


    The object name is always the last-but-one part of the full MTE name

    <attribute name>

    Response Time

    End of the example.
  5. The class of the MTE is output in the field MTE Class.

  6. To show the metric granularity, select the MTE in the previous screen, and choose (Show Details). The Monitor Attribute Detail Data screen appears. The Smoothed Performance Values for the Last 30 Minutes are shown under Performance Attributes, from which you can determine the data delivery frequency.


You should now have the following information, which you need later in the process, for the CCMS metric:

  • MTE class

  • instance-specific or system-wide; in the latter case, you also need the name of the context

  • Metric Type; whether it is a performance metric

  • For performance metrics, the measurement frequency (granularity)

  • Object name, if there are several MTEs of this class in a context.

The next section (Determining the Collector) tells you how to use this information to determine the collector to use in MAI.