Contact Us

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


  • 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.