SAP Business Technology Platform has quietly become one of the most strategically important pieces of the modern SAP landscape. As organizations accelerate their move to S/4HANA and expand into cloud-based processes, BTP, and its Integration Suite in particular, is increasingly the connective tissue holding it all together. It routes messages, orchestrates workflows, manages APIs, and bridges SAP and non-SAP systems across the enterprise.
That's a lot of responsibility for a platform that many operations teams aren't yet monitoring with the same rigor they apply to their core SAP systems.
Traditional SAP monitoring tools were built for a different world, one of on-premise ABAP stacks, HANA databases, and well-defined system boundaries. BTP is cloud-native, event-driven, and highly distributed. That mismatch creates a real operational blind spot.
SAP provides native observability through tools like SAP Cloud ALM and the BTP cockpit. However, these capabilities remain fragmented across services and lack end-to-end correlation with the broader SAP landscape. You can check Integration Suite logs in one place, certificate status in another, and resource consumption somewhere else entirely, all without any connection to the health of the broader SAP landscape those integrations are serving. When something breaks, you're piecing together the picture manually.
The risks that tend to go undetected until it's too late are exactly the ones that cause business disruption: failed message processing logs, expiring keystores and certificates, saturated datastores, and connection pool exhaustion. A broken integration flow doesn't just mean a technical error — it can mean orders not flowing, data not syncing, or compliance gaps that are difficult to explain after the fact.
IT-Conductor has always been built around the idea that SAP operations should be managed holistically, not in fragments. Your ABAP systems, HANA databases, S/4HANA environments, and cloud integrations all affect each other — so your monitoring should reflect that.
That's why we're excited to announce that IT-Conductor now fully supports SAP Integration Suite monitoring. SAP Integration Suite environments can be onboarded into IT-Conductor and managed alongside the rest of your SAP landscape in a single, unified service grid. No more context-switching between tools. No more blind spots.
Here's what IT-Conductor monitors out of the box once your SAP Integration Suite environment is connected:
Availability & Heartbeat — real-time status and downtime detection for your BTP sub-account connection
Connection Failures & API Retriever Errors — immediate visibility into connectivity issues before they cascade
Integration Flows (iFlows) — message processing logs, failed MPLs, and overall execution status across your integration flows
Keystores & PGP Keys — days-to-expiration tracking so you're never caught off guard by a lapsed certificate
Resource Usage — datastore consumption, message throughput, API usage, and service-level limits
Service Endpoints — availability and responsiveness of the interfaces your external systems depend on
Figure 2: Monitoring SAP BTP Integration Suite metrics in IT-Conductor
One of the things we focused on when building this capability was making the onboarding experience as straightforward as possible. You don't need to deploy agents or make significant changes to your BTP environment. The setup follows a clean, API-based approach:
In your BTP subaccount, verify that the Process Integration Runtime service is assigned under Entitlements, and that a Cloud Foundry environment and space are in place.
From the Service Marketplace, create a new Process Integration Runtime instance using the API plan, which is typically intended for API-based access and monitoring scenarios rather than message processing.
Generate a service key (Client ID/Secret type) from the instance, and save the credentials: URL, Token URL, Client ID, and Client Secret.
In IT-Conductor, enter your host details and the token/service URL from step 3, then provide the Client ID and Secret on the following screen.
Once credentials are configured, your SAP Integration Suite environment can typically appear in the IT-Conductor service grid within minutes.
Full step-by-step instructions, including screenshots for every stage, are available in our BTP monitoring documentation.
SAP is making no secret of the fact that BTP is central to its long-term product direction. The more your organization leans on SAP Integration Suite to connect critical systems, the more a failure there becomes a business-critical event — not just an IT issue.
Monitoring it as an afterthought, or relying on manual log reviews and reactive alerting, isn't a sustainable approach as your integration footprint grows. The same operational discipline that keeps your core SAP systems healthy needs to extend to the integrations that tie everything together.
With IT-Conductor's SAP Integration Suite support, now it can.
Already an IT-Conductor customer? You can start onboarding your SAP Integration Suite environment today using our step-by-step documentation.
New to IT-Conductor? See how we bring unified monitoring to your entire SAP landscape.