Skip to content
Menu
Guide

How to monitor SAP Integration Suite: what to watch and how to respond

Monitor SAP Integration Suite in layers. Watch message status and deployed content in Cloud Integration, API traffic and policy errors in API Management, event delivery in advanced event mesh, and connectivity and cluster health for Cloud Connector and Edge Integration Cell. Route alerts to owners with runbooks, and agree who may change what.

Published 2026-10-06By Spanovix
01Key takeaways

What you will learn

  1. Monitor each runtime area separately, because each one fails in its own way.
  2. Design interfaces for monitoring with correlation IDs, idempotency, retries with backoff and dead letter handling.
  3. Send alerts to named owners and attach a runbook to every alert.
  4. Control access and change with segregation of duties, four-eyes approval and time-limited break-glass access.
  5. Build the monitoring model before the first PI/PO migration wave, not after.

For CIOs, integration architects and heads of SAP centres of excellence who run or plan to run SAP Integration Suite.

02Read the guide

What monitoring has to cover

SAP Integration Suite is not one runtime with one screen. It is a set of capabilities, and each one produces different signals and fails in a different way. Cloud Integration runs integration flows. API Management exposes API proxies. Advanced event mesh moves events. Edge Integration Cell can run integration flows and API proxies inside your own landscape. SAP Cloud Connector links SAP BTP to on-premise systems.

A workable monitoring design starts from business impact, then maps each interface to the runtime area that carries it. The sections below describe what to watch in each area. The steps afterwards turn that into an operating model.

What to watch, by runtime area

Cloud Integration

Cloud Integration gives you message processing logs, trace and log levels, and a monitor for message status and deployed content. These are the daily tools of first-line support.

Watch these signals:

  • Message status per interface, especially failed and retrying messages.
  • The state of deployed content. An integration flow that is not running is a silent outage for the interface it serves.
  • Repeated failures with the same error text, which usually point to a design problem and not to bad data.
  • Trace and log levels. Keep them at the lowest level that supports your team, and raise them for a bounded time when diagnosing. Payloads can contain personal or commercial data, so agree masking rules before anyone switches on detailed tracing.

API Management

API Management offers API proxies, policies, an API developer portal, products and analytics. Monitor at the level of the API proxy and the product.

Watch these signals:

  • Traffic, error and response time trends per API proxy, using the analytics.
  • Rejections from OAuth 2.0 verification, which show expired credentials or misconfigured consumers.
  • Quota and spike arrest violations.
  • Rejections from JSON and XML threat protection, which can be harmless malformed calls or the first sign of abuse.

Choose to contact the consumer when quota violations come from one application. Choose to review the product limits when many consumers hit the same limit.

Continue reading

Full guide and PDF

Get the monitoring playbook

  • Alert and runbook templates per runtime area
  • Role and access model with break-glass rules
  • Pre-go-live monitoring checklist for migration waves

We use your details to send this and to follow up about it. Nothing else.

03

Questions

What does Cloud Integration give me for monitoring out of the box?

Cloud Integration provides message processing logs, trace and log levels, and a monitor for message status and deployed content. These cover the daily support work. For alerting and cross-system views you add SAP Alert Notification service and SAP Cloud ALM.

Which tool should raise alerts for SAP Integration Suite?

SAP Alert Notification service can raise alerts, and SAP Cloud ALM provides integration and exception monitoring across SAP cloud and on-premise components. Choose the alerting service for routing to teams, and Cloud ALM for a cross-component view. Most operating models use both.

Do I monitor Edge Integration Cell differently?

Content is designed and monitored in the cloud, but the runtime runs on your own customer-managed Kubernetes cluster. You therefore monitor integration content as usual and also take responsibility for cluster health, capacity and maintenance in your own landscape.

How does API Management monitoring differ from integration flow monitoring?

API Management monitoring centres on API proxies, products and analytics, plus policy outcomes such as OAuth 2.0 verification, quota, spike arrest and threat protection rejections. Integration flow monitoring centres on message status, processing logs and deployed content.

When should monitoring be in place for a PI/PO migration?

Before the first migration wave. SAP Process Orchestration 7.5 has mainstream maintenance until 31 December 2027 and optional extended maintenance until 31 December 2030. A tested monitoring and support model lets you run old and new platforms in parallel safely.

See Spanovix on your landscape

A short working session with our team, focused on your interfaces, your controls and your goals.