- SAP Managed Tags
One of SAP’s core strategic goals is to empower IT teams by simplifying complexity and seamlessly integrating diverse systems, whether they’re SAP or not. In today's enterprise environments, organizations rely on a wide array of tools, platforms, and custom applications. Recognizing this, SAP aims to provide a centralized, unified platform where all of these components, cloud-native services, third-party systems can be monitored, managed, and optimized from one place: Cloud ALM.
This is a powerful cloud-native solution built to manage the entire lifecycle of both SAP and non-SAP applications, from initial deployment to ongoing operations. With its real-time insights and proactive capabilities, it gives you a holistic view of your IT landscape, helping ensure system health, detect issues early, and maintain governance regardless of where your workloads are running or how your architecture is structured.
What does this blog covers?
In this post, we’ll dive into how SAP Cloud ALM can integrate with non‑SAP applications, and review the available scenarios and methods to connect external systems and fully leverage its monitoring capabilities.
While SAP Cloud ALM already offers out-of-the-box (plug-and-play) integrations with well-known platforms like Microsoft Teams, Jira, ServiceNow, Tricentis, Signavio, and WalkMe, it also provides flexible integration paths for any non‑SAP solution. Let’s explore some key facts:
Cloud ALM Integration Key Facts for Non‑SAP Applications:
1. Open Platform Architecture
Cloud ALM is built on open standards. It can monitor any application capable of sending telemetry data (metrics, logs, traces) using OpenTelemetry or structured event messages.
2. Support for Custom Applications on SAP BTP
Custom applications running on SAP BTP (Cloud Foundry or Kyma) can be monitored natively using Java or Node.js OpenTelemetry SDKs.
3. Multiple Monitoring Modules
Integration & Exception Monitoring: For structured logs, message flows, and application-level errors.
Health Monitoring: For performance and availability KPIs, especially in custom BTP-based applications.
4. Native OpenTelemetry Support
Any OpenTelemetry-compatible application, inside or outside SAP, can integrate via the Raw Data Inbound API, enabling deep observability for microservices, SaaS, and hybrid environments.
Important:
Due to the fact these are all external (non‑SAP) systems, there are no pre-built native connectors. Instead, integration is performed via robust and secure APIs offered by SAP Cloud ALM:
- Inbound API: for sending structured events and exception messages
- Raw Data Inbound API (OpenTelemetry): for sending telemetry data such as metrics, logs, and traces
- Analytics, Landscape & Event APIs: for reading system data and enabling external dashboards or alerts
API integration is the standard approach. There are no native connectors for non-SAP platforms.
Monitoring Scenarios for Non-SAP Systems:
Note: The content of the scenarios described in this document is subject to change. SAP continuously evolves the capabilities of Cloud ALM, including support for additional third-party systems and integration scenarios. Please refer to the SAP Cloud ALM Expert Portal for the most up-to-date information.
In addition, you can monitor non‑SAP applications via SAP Cloud ALM. However, you must manually develop the integration using the available telemetry ingestion APIs (e.g., Raw Data Inbound for Logs and Metrics).
The support is not yet fully plug‑and‑play or “native” as it is for SAP-managed systems.
1. Monitoring Microservices and Containerized Environments (Kubernetes, Docker)
Scenario: Observability for microservices and their orchestration within container platforms like Kubernetes or Docker.
Solution: Use the Raw Data Inbound API to ingest OpenTelemetry data into Cloud ALM, leveraging Health and Exception Monitoring.
Reference: https://github.com/SAP-samples/alm-demo-session
2. Monitoring Middleware and Integration Platforms
Scenario: Centralizing observability across CI/CD pipelines.
Solution: Use Operations APIs or Event Inbound API to track deployments, builds, and failures.
Reference: https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/integration-monitoring.html?an...
3. Monitoring Third-Party SaaS Applications
Scenario:Monitoring mission-critical SaaS platforms outside SAP
Solution: Register systems as Non-SAP Services and integrate via their APIs or agents using SAP’s Raw Data or Event APIs.
4. Monitoring DevOps and CI/CD Pipelines
Scenario: CI/CD pipelines (Jenkins, Azure DevOps) automate deployments of both SAP and non-SAP applications, but often lack centralized observability.
Solution: Use Operations APIs or Event Inbound API to track deployments, builds, and failures.
Reference: https://architecture.learning.sap.com/docs/ref-arch/1c5706feb5
5. Monitoring Data Platforms and Databases
Scenario: Analytical workloads run across platforms.
Solution: Use custom scripts to extract KPIs and forward data via OpenTelemetry to Cloud ALM.
NOTE: No direct SAP reference available for external DBs, but uses the same OpenTelemetry-based pattern via Raw Data Inbound API. For general telemetry integration, refer to:)
https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/data-collection-infrastructure...
How to get started:
Here are the official guides to help you implement any scenario described above:
Adding Non-SAP Services and Systems | SAP Help Portal
Non-SAP Services and Systems
Integrate CI/CD with cTMS as part of SAP Cloud ALM
OpenTelemetry@SAP
SAP Cloud ALM APIs for Operations
Integration & Exception Monitoring - Setup & Configuration
SAP ALM API & Integration: Open Telemetry Support ... - SAP Community
Bluesky| User | Count |
|---|---|
| 127 | |
| 37 | |
| 36 | |
| 19 | |
| 17 | |
| 15 | |
| 12 | |
| 12 | |
| 10 | |
| 8 |
