Integration & Exception Monitoring

The purpose of Integration & Exception Monitoring is to provide transparency for the data exchange processes. It supports the monitoring for peer-to-peer interfaces as well as interfaces using orchestration platforms and provides a unified user experience for all interface types using a common look-and-feel and handling pattern.

Integration & Exception Monitoring closes the gap between IT and Business. The correlation of integration artifacts provides end-to-end visibility in interface calls and message flows cross all involved cloud services and systems. Users of Integration & Exception Monitoring can analyze the actual processing of interface calls and message flows including possible technical or business-driven root causes.

Integration & Exception Monitoring provides the following functionalities:

  • Message Monitoring
  • Message Search (Tracking)
  • Alerting on failed messages or exceptions

Features

  • Monitoring
    Monitoring provides a detailed status overview per business system (not available in beta) and/or cloud components on the incoming/outgoing messages for different interfaces. Components can be organized in scenarios to describe message flow paths between them. Via drill down to single messages, customers can check individual issues and message details.
  • Alerting
    Based on the collected data, alerts for certain error situations can be defined, e.g. messages in status ERROR on a specific component or in a specific scenario. Generated alerts are collected into the Alert Inbox. To analyze the alert, the user can drill down in the alert details to get information on the related message details. In the Alert Inbox, it is possible to perform actions like assign a processor, add comments, postpone, or confirm an alert.
  • Tracking
    Tracking allows users to search and track single messages based on specific (business) context attributes like the order number, employee id, or similar context attributes. As a prerequisite (business) context information must be exposed by the relevant component and send together with the message's log fragments to SAP Cloud ALM. Examples are e.g. custom header attributes in SAP Cloud Platform Integration or a single message-id. The search is executed cross-component and cross-category.

Frequently Asked Questions (FAQs)

Integration & Exception Monitoring in SAP Cloud ALM supports the monitoring of numerous managed components (services and systems). Each managed component has its own statuses and their definitions for messages. It is tedious to populate, categorize, and standardize such an extensive list from different managed components. Therefore, status groups were introduced to simplify this process and offer a concise collection of statuses.

Status group is a SAP Cloud ALM concept. A status group is a collection of statuses grouped based on their logical definition. There are 7 unique status groups in SAP Cloud ALM:

  • ERROR
  • WARNING
  • IN PROCESS
  • CANCELED
  • SUCCESSFUL
  • INFO
  • OTHERS

All statuses maintained by a managed component fall into any one of the status groups in SAP Cloud ALM. For instance, AIF Messages with SUCCESSFUL status fall under SUCCESSFUL status group. While, APPLICATION ERROR and TECHNICAL ERROR statuses fall under ERROR status group. Rather than including multiple statuses like APPLICATION ERROR and TECHNICAL ERROR to filter error messages, you can use the ERROR status group.  

Please note that the mapping of status to status group differs for different managed components.

Usage of Status and Status Groups

When you are configuring filters, and are sure about the status of messages (defined in the managed component) that needs to be monitored, you can use the Status parameter.

Whereas, if you are unsure about the exact statuses (defined in the managed component) that need to be monitored, you can use the Status Group parameter.

Supported Products

For setup details please follow the links provided on page Integration & Exception Monitoring - Setup & Configuration.