Show TOC

Procedure documentationCoupling to the Monitoring and Alerting Infrastructure Locate this document in the navigation structure

 

To use the central SAP Solution Manager Alert Inbox to view and handle alerts, and to automatically create notifications and incidents for exceptions, you have to explicitly couple exception management to the Monitoring and Alerting Infrastructure (MAI).

You do this in the system monitoring configuration, by creating a custom template with customer-specific metric groups and corresponding alerts, at the level of a technical system, and then assigning the custom template to your systems.

Exception management provides the following data providers for MAI to collect exceptions from the central exception store:

  • Exception Collector (SE)

    Collects single exceptions for a specified selection parameter and technical system that have occurred since the last collection.

  • Exception Collector (MSE_PF)

    Collects multiple-step process flow exceptions per category/subcategory that have occurred since the last collection.

Procedure

Create Custom Template

  1. In SAP Solution Manager Configuration (transaction solman_setup), choose   Technical Monitoring   System Monitoring  .

  2. In the Template Maintenance step, create a custom template based on an existing template.

    Recommendation Recommendation

    Base your template one of the templates below Technical System, either a new generic product template, or within a customer template for the relevant system.

    End of the recommendation.

  3. Follow the instructions provided in the help area.

Create Metric Groups

You create one metric group, with variants, per data provider.

  1. Switch to expert mode, and then choose   Create   Metric  . A guided procedure starts.

  2. On the Overview tab page, specify the following:

    • Name

    • Metric category: Exceptions

    • Metric class: Metric group

    • Raise alert per variant: selected

  3. On the Data Source tab page, specify the following:

    • Collection interval

    • Data collector: RFC (pull)

    • Data provider for single exceptions: Exception Collector (SE)

      • Collector input parameters:

        • SOURCE (EM implementation source): required

        • SUBCATEG (EM subcategory): optional

        • USER: optional

      • Add the desired variants for the SOURCE parameter:

        • ABAP_WS for ABAP Web service exceptions

        • ABAP_DUMP for ABAP short dumps

        • ABAP_JOBS for ABAP job errors

        • ABAP_SLOG for ABAP system log errors

        • ABAP_APLOG for ABAP application log errors

        • ABAP_UPDAT for ABAP update errors

    • Data provider for multiple step exceptions: Exception Collector (MSE_PF)

      • Collector input parameters:

        • CATEGORY (EM process flow category ID): required

        • SUBCATEG (EM process flow subcategory ID): optional

  4. On the Threshold tab page, select Already Rated as the threshold type.

  5. On the Others tab page, enter the technical name of the metric.

  6. Finish the guided procedure.

Create Alerts and Assign to Metrics

  1. Choose   Create   Alert  .

  2. Follow the instructions in the guided procedure to define the alert configuration and assign it to the metric groups.

Assign Custom Template to System

  1. In the Define Scope step of the system monitoring configuration, choose the systems to be monitored.

  2. In the Setup Monitoring step, assign the template you created to the systems.

Result

You can now handle exceptions using the central SAP Solution Manager Alert Inbox.

You can also monitor your metrics in the System Monitoring view of the Technical Monitoring work center. For more information, see System Monitoring.

More Information

Technical Monitoring and Alerting