Docs / Monitoring / SAP Cloud ALM

SAP Cloud ALM Connectivity

ASAPIO Integration Add-on can push monitoring data to SAP Cloud ALM, making ASAPIO message flows visible alongside other SAP integration metrics in a centralized dashboard. Two data channels are supported: error rate metrics for the Health Monitoring dashboard, and exception logs for the Integration & Exception Monitoring dashboard.

Overview

SAP systems process a high volume of events originating from multiple objects and instances. These events produce requests that result in various outcomes — successful completions and errors alike. To maintain system health visibility, ASAPIO calculates the error ratio per object: the proportion of failed requests relative to total requests processed over a configurable time window.

This error rate metric is transmitted via API to SAP Cloud ALM's Health Monitoring dashboard, enabling proactive monitoring and timely identification of objects experiencing elevated error rates. Since the January 2026 release, exception messages can additionally be forwarded to the Integration & Exception Monitoring dashboard.

Prerequisites

APIs Used

Health Monitoring (Metrics)

See how ASAPIO health metrics are visualized in the SAP Cloud ALM Health Monitoring dashboard.

Exception Monitoring (Logs)

Watch the real-time flow of ASAPIO exception logs into the SAP Cloud ALM Integration & Exception Monitoring dashboard.

Metrics

Error rate data is transmitted via the Raw Data Inbound Metrics API. Each execution sends a single JSON file containing multiple metrics. The payload follows the OpenTelemetry format (key-value pairs) as required by the API.

Logs

Exception messages are transmitted via the Raw Data Inbound Logs API. Each execution sends a batch of log records conforming to the OpenTelemetry Protocol (OTLP) Logs format as required by the API.

Calculation Scope

Error rate metrics are calculated at the object level for a configurable time range (in minutes from the current time). Two scope options are available:

Configuration in SAP Cloud ALM

Retrieving Cloud ALM Credentials

All authentication data and configuration parameters are available at:

Administration → Landscape Management → Services & Systems → Configuration → SAP Cloud ALM Service Key

Download the existing service key file from this location — it contains the Client ID, Client Secret, and all required endpoint URLs.

Creating a Service for Health Monitoring (Metrics)

Step 1 — Create a new service

Navigate to Administration → Landscape Management → Services & Systems → Add → New Service and complete the required fields:

Step 2 — Add the service to the Health Monitoring scope

  1. Navigate to Operations → Health Monitoring.
  2. Click Select a Scope.
  3. Clear all existing filters, locate the service you created, select it, and click Apply.

Step 3 — Activate the service

  1. Open the Configuration tab.
  2. In the Services section, locate your service and toggle its status to ON.

Creating a Service for Integration & Exception Monitoring (Logs)

Step 1 — Create a new service

Navigate to Administration → Landscape Management → Services & Systems → Add → New Service and complete the same required fields as described above.

Step 2 — Add the service to the Integration & Exception Monitoring scope

  1. Navigate to Operations → Integration & Exception Monitoring.
  2. Click Select a Scope.
  3. Clear all existing filters, locate the service you created, select it, and click Apply.

Step 3 — Activate the service

  1. Open the Configuration tab.
  2. In the Services section, locate your service and toggle its status to ON.

Retrieving the Service ID

Navigate to Administration → Landscape Management → Services & Systems, select your service, and note the value in the ID field — this is your Service ID, required for the SAP system configuration below.

Configuration in the SAP System

Instance Default Values (SPRO)

Cloud ALM connectivity must be activated in the designated ASAPIO instances via SPRO customization (Connection and Replication Object Customizing). Configure the following parameters in the default values of your primary instance:

Default AttributeValue
CALM_INSTANCEInstance name pointing to the metrics endpoint
CALM_SERVICEIDService ID of the Health Monitoring service
CALM_LOGS_INSTANCEInstance name pointing to the logs endpoint
CALM_LOG_SERVICEIDService ID of the Integration & Exception Monitoring service

Cloud ALM Instance for Metrics

Create a Cloud ALM instance using RFC destination CLOUD_ALM_METRICS_API. Two RFC destinations of type G are required:

Set the following default values on the instance:

Default AttributeValue
AUTH_TYPEOAUTH
CLIENT_IDClient ID from the Cloud ALM service key
TOKEN_DESTINATIONCLOUD_ALM_METRICS_TOKEN

Cloud ALM Instance for Logs

Create a second Cloud ALM instance using RFC destination CLOUD_ALM_LOGS_API. Two RFC destinations of type G are required:

Set the following default values on the instance:

Default AttributeValue
AUTH_TYPEOAUTH
CLIENT_IDClient ID from the Cloud ALM service key
TOKEN_DESTINATIONCLOUD_ALM_LOGS_TOKEN