SAP Cloud ALM extension

Latest Dynatrace
Extension
Published Oct 15, 2026
Preview

Monitor SAP Cloud ALM health, jobs, integrations, and project analytics in Dynatrace with analytics metrics, OTel logs, and Real User Monitoring traces.

Get started

Overview

The SAP Cloud ALM extension integrates Dynatrace with the SAP Cloud ALM Analytics API and Raw Data Outbound APIs. It collects operational metrics from analytics data providers, ingests OTel-formatted logs, and forwards RUM traces to Distributed Tracing.

Use cases

Centralize SAP operational health by consolidating health metrics, job execution results, and integration message status from across the SAP landscape into Dynatrace dashboards and alerts.
Detect and alert on job failures: track aborted, warning, and error-state job executions across all monitored SAP systems.
Monitor integration message failure rates in SAP Integration Suite via Cloud ALM's CPI integration monitoring provider.
Correlate real user monitoring data (response times, request counts, user counts by request type) with backend service health to identify user-impacting issues.
Track synthetic monitoring scenario availability and performance ratings across business services.
Monitor business process KPIs over time and alert when values breach configured thresholds.
Assess business service SLA and SLO compliance using Business Service Management analytics.
Track implementation and project health: monitor defect counts, feature delivery status, requirements approval, task effort and completion, test results, and quality gate outcomes.
Audit configuration changes, store counts, and security records for compliance purposes via Configuration & Security Analysis.
Ingest raw OTel logs and traces from SAP Cloud ALM for root-cause analysis across business processes.

Requirements

SAP Cloud ALM subscription with the Operations module activated
SAP BTP service instance for the SAP Cloud ALM API, with all required scopes declared in the xs-security.authorities block at instance creation time (see SAP Cloud ALM API scopes)
Dynatrace API token with the openTelemetryTrace.ingest scope (required only when the Raw Data Outbound Traces feature is enabled)

Connectivity

The ActiveGate must have outbound HTTPS access to the SAP Cloud ALM API endpoint (obtained from the BTP service key).
The OAuth 2.0 token endpoint for the BTP service instance must be reachable from the ActiveGate.
The ActiveGate must have outbound HTTPS access to the Dynatrace environment API endpoint when traces are enabled.

Activation and setup

Setup has four steps. Create the SAP Cloud ALM API service instance in SAP BTP, activate the extension in Dynatrace Hub, create a monitoring configuration, and verify that data arrives. The prerequisites are listed under Requirements.

1. Create the SAP Cloud ALM API service instance

The extension authenticates with OAuth 2.0 client credentials from an SAP BTP service key.

In the SAP BTP cockpit, open the subaccount where SAP Cloud ALM is subscribed.
Go to Services > Instances and Subscriptions and select Create.
Select the SAP Cloud ALM API service and the standard plan, and enter an instance name.
In the Parameters step, paste the xs-security JSON with the scopes for the feature sets you plan to enable. See Example xs-security configuration for the BTP service instance.
Create the instance, then create a service key for it.
Copy these values from the service key:
- The API endpoint. Remove the trailing /api to get the SAP Cloud ALM Base URL, for example https://<tenant>.<region>.alm.cloud.sap.
- The uaa.url value. Append /oauth/token to get the SAP Cloud ALM Token URL, for example https://<tenant>.authentication.<region>.hana.ondemand.com/oauth/token.
- uaa.clientid and uaa.clientsecret.

You set scopes when you create the instance. To add one later, update the instance parameters and create a new service key. If a scope is missing, SAP Cloud ALM returns HTTP 403 for that provider and the extension skips it.

2. Activate the extension

Activate the SAP Cloud ALM extension in Dynatrace Hub. Activation deploys the extension package, which includes the collection code, metric and topology definitions, dashboards, and alert templates.

3. Create the monitoring configuration

Add a monitoring configuration and select an ActiveGate group that can reach SAP Cloud ALM (see Connectivity). Each configuration monitors one SAP Cloud ALM tenant.

Connection and authentication

Field	Required	Description
SAP Cloud ALM Base URL	Yes	`https://<tenant>.<region>.alm.cloud.sap`, without `/api` and without a trailing slash.
Authentication Type	Yes	OAuth for production tenants. API Key works only with the SAP Business Accelerator Hub sandbox (`https://sandbox.api.sap.com`). Default: OAuth.
SAP Cloud ALM Token URL	Yes, for OAuth	`uaa.url` from the service key, followed by `/oauth/token`.
Use credential vault	No	Read the client ID and secret from a Dynatrace credential vault entry instead of entering them here. Default: off.
Select vault credentials	Yes, with credential vault	A `USERNAME_PASSWORD` credential. Set the username to the client ID and the password to the client secret.
SAP Cloud ALM Client ID / Client Secret	Yes, for OAuth without vault	`uaa.clientid` and `uaa.clientsecret` from the service key.
SAP Cloud ALM API Key	Yes, for API Key	Your SAP Business Accelerator Hub API key.
Proxy	No	Proxy address, for example `http://proxy.example.com:8080`, with an optional username and password. Set it when the ActiveGate needs a proxy to reach SAP Cloud ALM.

Analytics providers

Each analytics provider maps to a feature set, and the extension only polls providers whose feature set is enabled. See Feature sets.

Field	Description
Frequency for Analytics Providers	Polling interval per provider, from 1 to 1440 minutes. The extension polls unlisted providers every minute. Use longer intervals for slow-changing project data such as Projects, Tasks, or Tests Analytics.
Project Filters > Project State	Collect data for Active, Archived, or All projects. Default: Active. Applies to Projects, Defects, Requirements, Tasks, and Tests Analytics.
Project Filters > Project Name Filter	Include only projects whose name contains one of the listed values (case-sensitive). Leave empty to include all projects.
Project Filters > Per-Provider Project Filters	Override the project name filter for a single provider, for example to narrow Tasks Analytics on large tenants without narrowing the others.
KPI Filters > KPI Name Filter	Business Process Monitoring only. Include only KPIs whose name contains one of the listed values (case-sensitive).
Real User Monitoring Filters > Capture User Name and Request Information	When on, the extension ingests RUM data as log events with user and request details, and stops reporting RUM metrics. Requires the `calm-api.rum.personal.read` scope and the Real User Monitoring feature set. Default: off.

Optional raw data outbound and BSM event sources

You set up these sources in the monitoring configuration. They're independent of feature sets. See Raw data outbound configuration.

OTel Logs Sources: Add one entry per log provider, up to 20. For each entry, set:
- Frequency (minutes): Polling interval, from 1 to 60 minutes. Default: 5.
- Lookback Period: Time window per request. Default: 5M. Keep it at least as long as the frequency to avoid gaps.
- Service Names: Optional. Leave empty to use all services discovered from the analytics providers.
- Provider-specific filters, such as exception status for exm.*, event domain and source for bsm, use case for iep, and job type and name for jam.*. For im, IM Category is required (for example, SAP Integration Suite Messages). If it's empty, the extension skips the im source.
OTel Traces Sources: Add up to five RUM trace sources, with frequency from 1 to 30 minutes and an optional request type filter. Also fill in Dynatrace Trace Ingest Configuration:
- Dynatrace Environment URL, for example https://<environment-id>.live.dynatrace.com.
- Dynatrace API Token with the openTelemetryTrace.ingest scope.
- Optional: Custom CA Certificate Path on the ActiveGate host, or Skip Certificate Validation (not recommended for production).
BSM Service Events Sources: Polls the BSM Service Events API (bsm-service/v1/events) and ingests individual Disruption, Degradation, Maintenance, and other events as log events. Requires calm-api.bsm.read. You can filter by service class (BusinessService, CloudService, TechnicalSystem), event type, service name, and service type.

Feature sets and logging

Select the feature sets to collect. Enable only the feature sets whose scopes are on the BTP service instance.
Log Level: Info by default. Set it to Debug only while troubleshooting.

4. Verify data collection

Open the monitoring configuration and check that its status is OK. A 403 error in the status or the extension log means a scope is missing for an enabled feature set.
After a few minutes, run the following query in Notebooks to confirm that metrics are arriving:
```
timeseries requests = sum(sap.calm.totalApiRequests), by: {cloud.alm.instance}
```
This metric requires the Cloud ALM API Metrics feature set.
If you configured OTel Logs Sources or BSM Service Events Sources, check for log events:
```
fetch logs
| filter isNotNull(cloud.alm.instance)
| limit 20
```
If you configured OTel Traces Sources, open Distributed Tracing and check for traces from SAP Cloud ALM.

Details

SAP Cloud ALM API scopes

You set scopes on the BTP service instance when you create it. A request made with a token that lacks a required scope returns HTTP 403.

Base analytics API scopes

These two scopes are required for all analytics data providers:

Scope	Purpose
`calm-api.analytics.read`	Access to all Analytics API data providers
`calm-api.analytics.providers.read`	Access to the provider catalog (`GET /analytics/providers`)

Per-provider analytics scopes

Each analytics feature set requires its own scope in addition to the base analytics API scopes. "Personal" scopes expose user-identifiable data (processor names, responsible users, tester IDs) and are optional. Omit them if personal data access isn't required.

Scope	Provider ID	Feature Set	Notes
`calm-api.hm.read`	`HM_ANALYTICS_DP`	Health Monitoring
`calm-api.bm.read`	`KPI_HISTORY_TOTALS`	Business Process Monitoring
`calm-api.iep.read`	`EVENTS`	Monitoring Events
`calm-api.bsm.read`	`EVENTS_DATA_SET`	Status Events	Also covers BSM analytics and the Raw Logs `bsm` provider
`calm-api.jobs.read`	`DP_JOB_MONITORING`	Job Monitoring
`calm-api.exm.read`	`EXM_DATAPROVIDER`	Exception Monitoring
`calm-api.integration-monitoring.read`	`CPI_MESSAGES`	Integration Monitoring	Also covers all integration provider variants
`calm-api.rum.read`	`DP_RUM_REQUEST_TYPES`	Real User Monitoring
`calm-api.rum.personal.read`	`DP_RUM_REQUEST_TYPES`	Real User Monitoring	Optional (personal/user data)
`calm-api.sum.read`	`SUM_DATAPROVIDER`	Synthetic User Monitoring
`calm-api.bsm.read`	`BSM_ANALYTICS_PROVIDER`	Business Services Analytics	Same scope as Status Events
`calm-api.csa.read`	`CCDB_STORE_DATA`	Configuration & Security Analysis
`calm-analytics.projects.read`	`DP_PROJECTS`	Projects Analytics	Public project data
`calm-api.projects.protected.read`	`DP_PROJECTS`	Projects Analytics	Protected project data
`calm-api.projects.private.read`	`DP_PROJECTS`	Projects Analytics	Private project data
`calm-api.defects.read`	`DP_DEFECTS`	Defects Analytics
`calm-api.defects.personal.read`	`DP_DEFECTS`	Defects Analytics	Optional (processor user data)
`calm-api.features.read`	`DP_FEATURES`	Features Analytics
`calm-api.features.personal.read`	`DP_FEATURES`	Features Analytics	Optional (responsible user data)
`calm-api.requirements.read`	`DP_REQUIREMENTS`	Requirements Analytics
`calm-api.requirements.personal.read`	`DP_REQUIREMENTS`	Requirements Analytics	Optional (processor user data)
`calm-api.tasks.read`	`DP_TASKS`	Tasks Analytics	Also covers tasks, defects, and requirements data
`calm-api.tasks.personal.read`	`DP_TASKS`	Tasks Analytics	Optional (processor user data)
`calm-api.tests.read`	`DP_TESTS`	Tests Analytics
`calm-api.tests.personal.read`	`DP_TESTS`	Tests Analytics	Optional (tester ID data)
`calm-api.qgates.read`	`DP_QGATES`	Quality Gates Analytics
`calm-api.qgates.personal.read`	`DP_QGATES`	Quality Gates Analytics	Optional (processor user data)

Raw Data Outbound Logs API

Endpoint: GET /api/calm-logs/v1/logs
Documentation: Raw Data Outbound Logs

Scope	Log Provider(s)
`calm-api.bsm.read`	`bsm`: Business Services Management events
`calm-api.exm.read`	`exm.im`, `exm.jam`: Exception Monitoring
`calm-api.integration-monitoring.read`	`im`: Integration Monitoring
`calm-api.iep.read`	`iep`: Monitoring Events
`calm-api.jobs.read`	`jam.def`, `jam.run`, `jam.run_step`: Job Automation Monitoring

Raw Data Outbound Traces API

Endpoint: GET /api/calm-traces/v1/traces
Documentation: Raw Data Outbound Traces

Scope	Traces Provider
`calm-api.rum.read`	`rum`: Real User Monitoring traces

Example xs-security configuration for the BTP service instance

The following example includes the scopes for all non-personal feature sets (recommended and optional). Remove the scopes for any feature sets you don't enable.

{
  "xs-security": {
    "xsappname": "CALMExtensionAPI",
    "authorities": [
      "$XSMASTERAPPNAME.calm-api.analytics.read",
      "$XSMASTERAPPNAME.calm-api.analytics.providers.read",
      "$XSMASTERAPPNAME.calm-api.hm.read",
      "$XSMASTERAPPNAME.calm-api.bm.read",
      "$XSMASTERAPPNAME.calm-api.iep.read",
      "$XSMASTERAPPNAME.calm-api.bsm.read",
      "$XSMASTERAPPNAME.calm-api.jobs.read",
      "$XSMASTERAPPNAME.calm-api.exm.read",
      "$XSMASTERAPPNAME.calm-api.integration-monitoring.read",
      "$XSMASTERAPPNAME.calm-api.rum.read",
      "$XSMASTERAPPNAME.calm-api.sum.read",
      "$XSMASTERAPPNAME.calm-api.csa.read",
      "$XSMASTERAPPNAME.calm-analytics.projects.read",
      "$XSMASTERAPPNAME.calm-api.projects.protected.read",
      "$XSMASTERAPPNAME.calm-api.projects.private.read",
      "$XSMASTERAPPNAME.calm-api.defects.read",
      "$XSMASTERAPPNAME.calm-api.features.read",
      "$XSMASTERAPPNAME.calm-api.requirements.read",
      "$XSMASTERAPPNAME.calm-api.tasks.read",
      "$XSMASTERAPPNAME.calm-api.tests.read",
      "$XSMASTERAPPNAME.calm-api.qgates.read"
    ]
  }
}

Raw data outbound configuration

Configure raw data outbound sources in the monitoring configuration under otel_logs_sources and otel_traces_sources. To enable a source, add its provider value to the corresponding list. Raw data outbound sources are separate from feature sets.

Logs API providers

Provider Value	Description	Required SAP Cloud ALM Setting
`exm.im`	Exception Monitoring (Integration Monitoring)	None
`exm.jam`	Exception Monitoring (Job Automation Monitoring)	None
`bsm`	Business Services Management status events	None
`im`	Integration Monitoring	The `category` parameter is mandatory
`iep`	Monitoring Events	Store Event Payload for 24 Hours must be enabled in SAP Cloud ALM
`jam.def`	Job Automation Monitoring (Definition Logs)	None
`jam.run`	Job Automation Monitoring (Runtime Logs)	None
`jam.run_step`	Job Automation Monitoring (Runtime Step Logs)	None

Log records are ingested as Dynatrace log events via the Extensions SDK report_log_event() call.

Traces API providers

Provider Value	Description
`rum`	Real User Monitoring traces (OTel `resourceSpans`)

Traces are forwarded to the Dynatrace OTel Trace Ingest API (POST /api/v2/otlp/v1/traces). Configure a Dynatrace API token with the openTelemetryTrace.ingest scope in the monitoring configuration under dt_trace_ingest.

Service discovery

The extension auto-discovers serviceId values from Analytics API provider data. By default, all discovered services are included for each enabled Raw Data Outbound provider. To restrict collection to specific services, provide a list of service names (not IDs) in the service_names configuration field. The extension resolves names to IDs at runtime.

Entity topology

The extension creates the following Dynatrace entity types:

Entity Type	Identified By	Relationship
`sap:cloud_alm_instance`	`cloud.alm.instance` dimension	Root entity
`sap:cloud_alm_instance_analytics_provider`	`cloud.alm.instance` + `providername`	`CHILD_OF` → instance
`sap:cloud_alm_instance_service`	`cloud.alm.instance` + `servicename`	`CHILD_OF` → instance

Analytics provider entities are also PART_OF the corresponding service entity when service data is present.

Feature sets

When activating your extension using a monitoring configuration, you can limit monitoring to one of the feature sets. To work properly, the extension has to collect at least one metric after the activation.

In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.

All metrics that aren't categorized into any feature set are considered to be the default and are always reported.

A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.

DP_JOB_MONITORING

Metric name	Metric key	Description
Job Run Time	sap.calm.dp_job_monitoring.runtime	Total runtime of the job execution
Job Average Run Time	sap.calm.dp_job_monitoring.averageruntime	Average runtime of job executions
Job Executions	sap.calm.dp_job_monitoring.executions	Total number of job executions
Job Success Count	sap.calm.dp_job_monitoring.success	Number of successful job executions
Job Warning Count	sap.calm.dp_job_monitoring.warning	Number of job executions with warnings
Job Aborted Count	sap.calm.dp_job_monitoring.aborted	Number of aborted job executions
Job Application Warning Count	sap.calm.dp_job_monitoring.applicationwarning	Number of job executions with application warnings
Job Application Error Count	sap.calm.dp_job_monitoring.applicationerror	Number of job executions with application errors

DP_PROJECTS

Metric name	Metric key	Description
Project Status	sap.calm.dp_projects.status	Status of SAP Cloud ALM projects

EXM_DATAPROVIDER

Metric name	Metric key	Description
Exception Count	sap.calm.exm_dataprovider.counter	Total number of exceptions detected

HM_ANALYTICS_DP

Metric name	Metric key	Description
Health Metric Value	sap.calm.hm_analytics_dp.value	Current value of the health metric
Health Metric Limit	sap.calm.hm_analytics_dp.limit	Configured limit for the health metric
Health Metric Usage	sap.calm.hm_analytics_dp.usage	Current usage percentage of the health metric
Health OK Status Count	sap.calm.hm_analytics_dp.okstatus	Number of health metrics in OK status
Health Warning Status Count	sap.calm.hm_analytics_dp.warningstatus	Number of health metrics in warning status
Health Critical Status Count	sap.calm.hm_analytics_dp.criticalstatus	Number of health metrics in critical status

CCDB_STORE_DATA

Metric name	Metric key	Description
Number of Changes	sap.calm.ccdb_store_data.numchanges	Total number of configuration changes
Number of Stores	sap.calm.ccdb_store_data.numstores	Total number of configuration stores
Number of Items	sap.calm.ccdb_store_data.numitems	Total number of configuration items
Configuration Tickets	sap.calm.ccdb_store_data.tickets	Number of tickets associated with configuration stores
Configuration Alerts	sap.calm.ccdb_store_data.alerts	Number of alerts associated with configuration stores
Configuration Mails	sap.calm.ccdb_store_data.mails	Number of email notifications associated with configuration stores
Configuration Chat Messages	sap.calm.ccdb_store_data.chatmessages	Number of chat messages associated with configuration stores
Configuration Operation Flows	sap.calm.ccdb_store_data.operationflows	Number of operation flows associated with configuration stores

DP_TASKS

Metric name	Metric key	Description
Task Count	sap.calm.dp_tasks.counter	Total number of tasks
Task Story Points	sap.calm.dp_tasks.storypoint	Total story points for tasks
Task Effort	sap.calm.dp_tasks.effort	Total effort for tasks

EVENTS_DATA_SET

Metric name	Metric key	Description
Event Duration	sap.calm.events_data_set.duration	Duration of status events
Event Data Set Count	sap.calm.events_data_set.counter	Count of status events

DP_DEFECTS

Metric name	Metric key	Description
Defect Count	sap.calm.dp_defects.counter	Total number of defects in projects

DP_FEATURES

Metric name	Metric key	Description
Feature Count	sap.calm.dp_features.counter	Total number of features in projects

BSM_ANALYTICS_PROVIDER

Metric name	Metric key	Description
Business Service SLA	sap.calm.bsm_analytics_provider.sla	Service Level Agreement percentage for business services
Business Service SLO	sap.calm.bsm_analytics_provider.slo	Service Level Objective percentage for business services

EVENTS

Metric name	Metric key	Description
Event Count	sap.calm.events.events	Total number of monitoring events
Event Situations	sap.calm.events.eventsituations	Number of event situations detected
Event Total Duration	sap.calm.events.totalduration	Total duration of events
Event Tickets	sap.calm.events.tickets	Number of tickets created from events
Event Alerts	sap.calm.events.alerts	Number of alerts generated from events
Event Mails	sap.calm.events.mails	Number of email notifications sent for events
Event Chat Messages	sap.calm.events.chatmessages	Number of chat messages generated from events
Event Operation Flows	sap.calm.events.operationflows	Number of operation flows triggered by events

SUM_DATAPROVIDER

Metric name	Metric key	Description
SUM Not Available Count	sap.calm.sum_dataprovider.notavailable	Number of synthetic monitoring scenarios not available
SUM Available Count	sap.calm.sum_dataprovider.available	Number of synthetic monitoring scenarios available
SUM Availability Not Rated Count	sap.calm.sum_dataprovider.availabilitynotrated	Number of synthetic monitoring scenarios with availability not rated
SUM Execution Count	sap.calm.sum_dataprovider.executions	Total number of synthetic monitoring executions
SUM Critical Performance Count	sap.calm.sum_dataprovider.criticalperformance	Number of synthetic monitoring scenarios with critical performance
SUM Poor Performance Count	sap.calm.sum_dataprovider.poorperformance	Number of synthetic monitoring scenarios with poor performance
SUM Good Performance Count	sap.calm.sum_dataprovider.goodperformance	Number of synthetic monitoring scenarios with good performance
SUM Performance Not Rated Count	sap.calm.sum_dataprovider.performancenotrated	Number of synthetic monitoring scenarios with performance not rated
SUM Response Time	sap.calm.sum_dataprovider.responsetime	Response time for synthetic monitoring scenarios

DP_REQUIREMENTS

Metric name	Metric key	Description
Requirement Count	sap.calm.dp_requirements.counter	Total number of requirements in projects

Cloud ALM API Metrics

Metric name	Metric key	Description
Total API Requests	sap.calm.totalApiRequests	Total number of API requests made to SAP Cloud ALM
Total Response Size	sap.calm.totalResponseSize	Total size of API responses received from SAP Cloud ALM
Data Provider Execution Time	sap.calm.dpProviderExecutionTime	Time taken to execute the data provider API call
SAP Cloud ALM Service	sap.calm.services	Presence metric emitted once per (service, provider) pair to anchor topology node extraction and edges

DP_QGATES

Metric name	Metric key	Description
Quality Gate Count	sap.calm.dp_qgates.counter	Total number of quality gates
Quality Gate Checklist Count	sap.calm.dp_qgates.checklistcounter	Total number of quality gate checklist items

DP_TESTS

Metric name	Metric key	Description
Test Total	sap.calm.dp_tests.total	Total number of tests executed

DP_RUM_REQUEST_TYPES

Metric name	Metric key	Description
RUM Response Time	sap.calm.dp_rum_request_types.responsetime	Real user monitoring response time for requests
RUM User Count	sap.calm.dp_rum_request_types.users	Number of users making requests
RUM Request Count	sap.calm.dp_rum_request_types.requests	Total number of user requests
RUM OK Status Count	sap.calm.dp_rum_request_types.okstatus	Number of requests with OK status
RUM Warning Status Count	sap.calm.dp_rum_request_types.warningstatus	Number of requests with warning status
RUM Critical Status Count	sap.calm.dp_rum_request_types.criticalstatus	Number of requests with critical status

KPI_HISTORY_TOTALS

Metric name	Metric key	Description
KPI Value	sap.calm.kpi_history_totals.kpivalue	Key Performance Indicator value for business process monitoring

CPI_MESSAGES

Metric name	Metric key	Description
Integration Message Count	sap.calm.cpi_messages.count.gauge	Number of integration messages processed

Feature set metrics

You can enable or disable each feature set independently.

Recommended feature sets

Feature Set	Provider ID	Metrics
Cloud ALM API Metrics	None	Total API requests, response size, data provider execution time
Projects Analytics	`DP_PROJECTS`	Project status
Business Process Monitoring	`KPI_HISTORY_TOTALS`	KPI values by KPI ID, name, and category
Monitoring Events	`EVENTS`	Event count, situations, duration, tickets, alerts, notifications
Status Events	`EVENTS_DATA_SET`	Event duration and count by type and status
Health Monitoring	`HM_ANALYTICS_DP`	Value, limit, usage, OK/warning/critical status counts
Job Monitoring	`DP_JOB_MONITORING`	Executions, runtime, success, warning, aborted, app warning, app error
Defects Analytics	`DP_DEFECTS`	Defect count by project, scope, status, and priority
Features Analytics	`DP_FEATURES`	Feature count by project, scope, requirement, status, and priority
Requirements Analytics	`DP_REQUIREMENTS`	Requirement count by project, status, priority, and approval
Tasks Analytics	`DP_TASKS`	Task count, story points, and effort by type and status
Tests Analytics	`DP_TESTS`	Test totals by project, scope, type, and status
Quality Gates Analytics	`DP_QGATES`	Quality gate count and checklist count by project and status

Optional feature sets

Feature Set	Provider ID	Metrics
Exception Monitoring	`EXM_DATAPROVIDER`	Exception count by service and category
Integration Monitoring (SAP Integration Suite)	`CPI_MESSAGES`	Message count by service, artifact, and status group
Real User Monitoring	`DP_RUM_REQUEST_TYPES`	Response time, user count, request count, and status indicators by request type
Synthetic User Monitoring	`SUM_DATAPROVIDER`	Availability, performance ratings, executions, and response times
Business Services Analytics	`BSM_ANALYTICS_PROVIDER`	SLA and SLO percentages by business service
Configuration & Security Analysis	`CCDB_STORE_DATA`	Changes, stores, items, and notification counts per store

Explore in Dynatrace Hub

Monitor SAP Cloud ALM health, jobs, integrations, and project analytics in Dynatrace with analytics metrics, OTel logs, and Real User Monitoring traces.

SAP Cloud ALM extension

Latest Dynatrace
Extension
Published Oct 15, 2026
Preview

Monitor SAP Cloud ALM health, jobs, integrations, and project analytics in Dynatrace with analytics metrics, OTel logs, and Real User Monitoring traces.

Get started

Overview

Use cases

Centralize SAP operational health by consolidating health metrics, job execution results, and integration message status from across the SAP landscape into Dynatrace dashboards and alerts.
Detect and alert on job failures: track aborted, warning, and error-state job executions across all monitored SAP systems.
Monitor integration message failure rates in SAP Integration Suite via Cloud ALM's CPI integration monitoring provider.
Correlate real user monitoring data (response times, request counts, user counts by request type) with backend service health to identify user-impacting issues.
Track synthetic monitoring scenario availability and performance ratings across business services.
Monitor business process KPIs over time and alert when values breach configured thresholds.
Assess business service SLA and SLO compliance using Business Service Management analytics.
Track implementation and project health: monitor defect counts, feature delivery status, requirements approval, task effort and completion, test results, and quality gate outcomes.
Audit configuration changes, store counts, and security records for compliance purposes via Configuration & Security Analysis.
Ingest raw OTel logs and traces from SAP Cloud ALM for root-cause analysis across business processes.

Requirements

SAP Cloud ALM subscription with the Operations module activated
SAP BTP service instance for the SAP Cloud ALM API, with all required scopes declared in the xs-security.authorities block at instance creation time (see SAP Cloud ALM API scopes)
Dynatrace API token with the openTelemetryTrace.ingest scope (required only when the Raw Data Outbound Traces feature is enabled)

Connectivity

The ActiveGate must have outbound HTTPS access to the SAP Cloud ALM API endpoint (obtained from the BTP service key).
The OAuth 2.0 token endpoint for the BTP service instance must be reachable from the ActiveGate.
The ActiveGate must have outbound HTTPS access to the Dynatrace environment API endpoint when traces are enabled.

Activation and setup

1. Create the SAP Cloud ALM API service instance

The extension authenticates with OAuth 2.0 client credentials from an SAP BTP service key.

In the SAP BTP cockpit, open the subaccount where SAP Cloud ALM is subscribed.
Go to Services > Instances and Subscriptions and select Create.
Select the SAP Cloud ALM API service and the standard plan, and enter an instance name.
In the Parameters step, paste the xs-security JSON with the scopes for the feature sets you plan to enable. See Example xs-security configuration for the BTP service instance.
Create the instance, then create a service key for it.
Copy these values from the service key:
- The API endpoint. Remove the trailing /api to get the SAP Cloud ALM Base URL, for example https://<tenant>.<region>.alm.cloud.sap.
- The uaa.url value. Append /oauth/token to get the SAP Cloud ALM Token URL, for example https://<tenant>.authentication.<region>.hana.ondemand.com/oauth/token.
- uaa.clientid and uaa.clientsecret.

2. Activate the extension

Activate the SAP Cloud ALM extension in Dynatrace Hub. Activation deploys the extension package, which includes the collection code, metric and topology definitions, dashboards, and alert templates.

3. Create the monitoring configuration

Add a monitoring configuration and select an ActiveGate group that can reach SAP Cloud ALM (see Connectivity). Each configuration monitors one SAP Cloud ALM tenant.

Connection and authentication

Field	Required	Description
SAP Cloud ALM Base URL	Yes	`https://<tenant>.<region>.alm.cloud.sap`, without `/api` and without a trailing slash.
Authentication Type	Yes	OAuth for production tenants. API Key works only with the SAP Business Accelerator Hub sandbox (`https://sandbox.api.sap.com`). Default: OAuth.
SAP Cloud ALM Token URL	Yes, for OAuth	`uaa.url` from the service key, followed by `/oauth/token`.
Use credential vault	No	Read the client ID and secret from a Dynatrace credential vault entry instead of entering them here. Default: off.
Select vault credentials	Yes, with credential vault	A `USERNAME_PASSWORD` credential. Set the username to the client ID and the password to the client secret.
SAP Cloud ALM Client ID / Client Secret	Yes, for OAuth without vault	`uaa.clientid` and `uaa.clientsecret` from the service key.
SAP Cloud ALM API Key	Yes, for API Key	Your SAP Business Accelerator Hub API key.
Proxy	No	Proxy address, for example `http://proxy.example.com:8080`, with an optional username and password. Set it when the ActiveGate needs a proxy to reach SAP Cloud ALM.

Analytics providers

Each analytics provider maps to a feature set, and the extension only polls providers whose feature set is enabled. See Feature sets.

Field	Description
Frequency for Analytics Providers	Polling interval per provider, from 1 to 1440 minutes. The extension polls unlisted providers every minute. Use longer intervals for slow-changing project data such as Projects, Tasks, or Tests Analytics.
Project Filters > Project State	Collect data for Active, Archived, or All projects. Default: Active. Applies to Projects, Defects, Requirements, Tasks, and Tests Analytics.
Project Filters > Project Name Filter	Include only projects whose name contains one of the listed values (case-sensitive). Leave empty to include all projects.
Project Filters > Per-Provider Project Filters	Override the project name filter for a single provider, for example to narrow Tasks Analytics on large tenants without narrowing the others.
KPI Filters > KPI Name Filter	Business Process Monitoring only. Include only KPIs whose name contains one of the listed values (case-sensitive).
Real User Monitoring Filters > Capture User Name and Request Information	When on, the extension ingests RUM data as log events with user and request details, and stops reporting RUM metrics. Requires the `calm-api.rum.personal.read` scope and the Real User Monitoring feature set. Default: off.

Optional raw data outbound and BSM event sources

You set up these sources in the monitoring configuration. They're independent of feature sets. See Raw data outbound configuration.

OTel Logs Sources: Add one entry per log provider, up to 20. For each entry, set:
- Frequency (minutes): Polling interval, from 1 to 60 minutes. Default: 5.
- Lookback Period: Time window per request. Default: 5M. Keep it at least as long as the frequency to avoid gaps.
- Service Names: Optional. Leave empty to use all services discovered from the analytics providers.
- Provider-specific filters, such as exception status for exm.*, event domain and source for bsm, use case for iep, and job type and name for jam.*. For im, IM Category is required (for example, SAP Integration Suite Messages). If it's empty, the extension skips the im source.
OTel Traces Sources: Add up to five RUM trace sources, with frequency from 1 to 30 minutes and an optional request type filter. Also fill in Dynatrace Trace Ingest Configuration:
- Dynatrace Environment URL, for example https://<environment-id>.live.dynatrace.com.
- Dynatrace API Token with the openTelemetryTrace.ingest scope.
- Optional: Custom CA Certificate Path on the ActiveGate host, or Skip Certificate Validation (not recommended for production).
BSM Service Events Sources: Polls the BSM Service Events API (bsm-service/v1/events) and ingests individual Disruption, Degradation, Maintenance, and other events as log events. Requires calm-api.bsm.read. You can filter by service class (BusinessService, CloudService, TechnicalSystem), event type, service name, and service type.

Feature sets and logging

Select the feature sets to collect. Enable only the feature sets whose scopes are on the BTP service instance.
Log Level: Info by default. Set it to Debug only while troubleshooting.

4. Verify data collection

Open the monitoring configuration and check that its status is OK. A 403 error in the status or the extension log means a scope is missing for an enabled feature set.
After a few minutes, run the following query in Notebooks to confirm that metrics are arriving:
```
timeseries requests = sum(sap.calm.totalApiRequests), by: {cloud.alm.instance}
```
This metric requires the Cloud ALM API Metrics feature set.
If you configured OTel Logs Sources or BSM Service Events Sources, check for log events:
```
fetch logs
| filter isNotNull(cloud.alm.instance)
| limit 20
```
If you configured OTel Traces Sources, open Distributed Tracing and check for traces from SAP Cloud ALM.

Details

SAP Cloud ALM API scopes

You set scopes on the BTP service instance when you create it. A request made with a token that lacks a required scope returns HTTP 403.

Base analytics API scopes

These two scopes are required for all analytics data providers:

Scope	Purpose
`calm-api.analytics.read`	Access to all Analytics API data providers
`calm-api.analytics.providers.read`	Access to the provider catalog (`GET /analytics/providers`)

Per-provider analytics scopes

Scope	Provider ID	Feature Set	Notes
`calm-api.hm.read`	`HM_ANALYTICS_DP`	Health Monitoring
`calm-api.bm.read`	`KPI_HISTORY_TOTALS`	Business Process Monitoring
`calm-api.iep.read`	`EVENTS`	Monitoring Events
`calm-api.bsm.read`	`EVENTS_DATA_SET`	Status Events	Also covers BSM analytics and the Raw Logs `bsm` provider
`calm-api.jobs.read`	`DP_JOB_MONITORING`	Job Monitoring
`calm-api.exm.read`	`EXM_DATAPROVIDER`	Exception Monitoring
`calm-api.integration-monitoring.read`	`CPI_MESSAGES`	Integration Monitoring	Also covers all integration provider variants
`calm-api.rum.read`	`DP_RUM_REQUEST_TYPES`	Real User Monitoring
`calm-api.rum.personal.read`	`DP_RUM_REQUEST_TYPES`	Real User Monitoring	Optional (personal/user data)
`calm-api.sum.read`	`SUM_DATAPROVIDER`	Synthetic User Monitoring
`calm-api.bsm.read`	`BSM_ANALYTICS_PROVIDER`	Business Services Analytics	Same scope as Status Events
`calm-api.csa.read`	`CCDB_STORE_DATA`	Configuration & Security Analysis
`calm-analytics.projects.read`	`DP_PROJECTS`	Projects Analytics	Public project data
`calm-api.projects.protected.read`	`DP_PROJECTS`	Projects Analytics	Protected project data
`calm-api.projects.private.read`	`DP_PROJECTS`	Projects Analytics	Private project data
`calm-api.defects.read`	`DP_DEFECTS`	Defects Analytics
`calm-api.defects.personal.read`	`DP_DEFECTS`	Defects Analytics	Optional (processor user data)
`calm-api.features.read`	`DP_FEATURES`	Features Analytics
`calm-api.features.personal.read`	`DP_FEATURES`	Features Analytics	Optional (responsible user data)
`calm-api.requirements.read`	`DP_REQUIREMENTS`	Requirements Analytics
`calm-api.requirements.personal.read`	`DP_REQUIREMENTS`	Requirements Analytics	Optional (processor user data)
`calm-api.tasks.read`	`DP_TASKS`	Tasks Analytics	Also covers tasks, defects, and requirements data
`calm-api.tasks.personal.read`	`DP_TASKS`	Tasks Analytics	Optional (processor user data)
`calm-api.tests.read`	`DP_TESTS`	Tests Analytics
`calm-api.tests.personal.read`	`DP_TESTS`	Tests Analytics	Optional (tester ID data)
`calm-api.qgates.read`	`DP_QGATES`	Quality Gates Analytics
`calm-api.qgates.personal.read`	`DP_QGATES`	Quality Gates Analytics	Optional (processor user data)

Raw Data Outbound Logs API

Endpoint: GET /api/calm-logs/v1/logs
Documentation: Raw Data Outbound Logs

Scope	Log Provider(s)
`calm-api.bsm.read`	`bsm`: Business Services Management events
`calm-api.exm.read`	`exm.im`, `exm.jam`: Exception Monitoring
`calm-api.integration-monitoring.read`	`im`: Integration Monitoring
`calm-api.iep.read`	`iep`: Monitoring Events
`calm-api.jobs.read`	`jam.def`, `jam.run`, `jam.run_step`: Job Automation Monitoring

Raw Data Outbound Traces API

Endpoint: GET /api/calm-traces/v1/traces
Documentation: Raw Data Outbound Traces

Scope	Traces Provider
`calm-api.rum.read`	`rum`: Real User Monitoring traces

Example xs-security configuration for the BTP service instance

The following example includes the scopes for all non-personal feature sets (recommended and optional). Remove the scopes for any feature sets you don't enable.

{
  "xs-security": {
    "xsappname": "CALMExtensionAPI",
    "authorities": [
      "$XSMASTERAPPNAME.calm-api.analytics.read",
      "$XSMASTERAPPNAME.calm-api.analytics.providers.read",
      "$XSMASTERAPPNAME.calm-api.hm.read",
      "$XSMASTERAPPNAME.calm-api.bm.read",
      "$XSMASTERAPPNAME.calm-api.iep.read",
      "$XSMASTERAPPNAME.calm-api.bsm.read",
      "$XSMASTERAPPNAME.calm-api.jobs.read",
      "$XSMASTERAPPNAME.calm-api.exm.read",
      "$XSMASTERAPPNAME.calm-api.integration-monitoring.read",
      "$XSMASTERAPPNAME.calm-api.rum.read",
      "$XSMASTERAPPNAME.calm-api.sum.read",
      "$XSMASTERAPPNAME.calm-api.csa.read",
      "$XSMASTERAPPNAME.calm-analytics.projects.read",
      "$XSMASTERAPPNAME.calm-api.projects.protected.read",
      "$XSMASTERAPPNAME.calm-api.projects.private.read",
      "$XSMASTERAPPNAME.calm-api.defects.read",
      "$XSMASTERAPPNAME.calm-api.features.read",
      "$XSMASTERAPPNAME.calm-api.requirements.read",
      "$XSMASTERAPPNAME.calm-api.tasks.read",
      "$XSMASTERAPPNAME.calm-api.tests.read",
      "$XSMASTERAPPNAME.calm-api.qgates.read"
    ]
  }
}

Raw data outbound configuration

Logs API providers

Provider Value	Description	Required SAP Cloud ALM Setting
`exm.im`	Exception Monitoring (Integration Monitoring)	None
`exm.jam`	Exception Monitoring (Job Automation Monitoring)	None
`bsm`	Business Services Management status events	None
`im`	Integration Monitoring	The `category` parameter is mandatory
`iep`	Monitoring Events	Store Event Payload for 24 Hours must be enabled in SAP Cloud ALM
`jam.def`	Job Automation Monitoring (Definition Logs)	None
`jam.run`	Job Automation Monitoring (Runtime Logs)	None
`jam.run_step`	Job Automation Monitoring (Runtime Step Logs)	None

Log records are ingested as Dynatrace log events via the Extensions SDK report_log_event() call.

Traces API providers

Provider Value	Description
`rum`	Real User Monitoring traces (OTel `resourceSpans`)

Service discovery

Entity topology

The extension creates the following Dynatrace entity types:

Entity Type	Identified By	Relationship
`sap:cloud_alm_instance`	`cloud.alm.instance` dimension	Root entity
`sap:cloud_alm_instance_analytics_provider`	`cloud.alm.instance` + `providername`	`CHILD_OF` → instance
`sap:cloud_alm_instance_service`	`cloud.alm.instance` + `servicename`	`CHILD_OF` → instance

Analytics provider entities are also PART_OF the corresponding service entity when service data is present.

Feature sets

All metrics that aren't categorized into any feature set are considered to be the default and are always reported.

DP_JOB_MONITORING

Metric name	Metric key	Description
Job Run Time	sap.calm.dp_job_monitoring.runtime	Total runtime of the job execution
Job Average Run Time	sap.calm.dp_job_monitoring.averageruntime	Average runtime of job executions
Job Executions	sap.calm.dp_job_monitoring.executions	Total number of job executions
Job Success Count	sap.calm.dp_job_monitoring.success	Number of successful job executions
Job Warning Count	sap.calm.dp_job_monitoring.warning	Number of job executions with warnings
Job Aborted Count	sap.calm.dp_job_monitoring.aborted	Number of aborted job executions
Job Application Warning Count	sap.calm.dp_job_monitoring.applicationwarning	Number of job executions with application warnings
Job Application Error Count	sap.calm.dp_job_monitoring.applicationerror	Number of job executions with application errors

DP_PROJECTS

Metric name	Metric key	Description
Project Status	sap.calm.dp_projects.status	Status of SAP Cloud ALM projects

EXM_DATAPROVIDER

Metric name	Metric key	Description
Exception Count	sap.calm.exm_dataprovider.counter	Total number of exceptions detected

HM_ANALYTICS_DP

Metric name	Metric key	Description
Health Metric Value	sap.calm.hm_analytics_dp.value	Current value of the health metric
Health Metric Limit	sap.calm.hm_analytics_dp.limit	Configured limit for the health metric
Health Metric Usage	sap.calm.hm_analytics_dp.usage	Current usage percentage of the health metric
Health OK Status Count	sap.calm.hm_analytics_dp.okstatus	Number of health metrics in OK status
Health Warning Status Count	sap.calm.hm_analytics_dp.warningstatus	Number of health metrics in warning status
Health Critical Status Count	sap.calm.hm_analytics_dp.criticalstatus	Number of health metrics in critical status

CCDB_STORE_DATA

Metric name	Metric key	Description
Number of Changes	sap.calm.ccdb_store_data.numchanges	Total number of configuration changes
Number of Stores	sap.calm.ccdb_store_data.numstores	Total number of configuration stores
Number of Items	sap.calm.ccdb_store_data.numitems	Total number of configuration items
Configuration Tickets	sap.calm.ccdb_store_data.tickets	Number of tickets associated with configuration stores
Configuration Alerts	sap.calm.ccdb_store_data.alerts	Number of alerts associated with configuration stores
Configuration Mails	sap.calm.ccdb_store_data.mails	Number of email notifications associated with configuration stores
Configuration Chat Messages	sap.calm.ccdb_store_data.chatmessages	Number of chat messages associated with configuration stores
Configuration Operation Flows	sap.calm.ccdb_store_data.operationflows	Number of operation flows associated with configuration stores

DP_TASKS

Metric name	Metric key	Description
Task Count	sap.calm.dp_tasks.counter	Total number of tasks
Task Story Points	sap.calm.dp_tasks.storypoint	Total story points for tasks
Task Effort	sap.calm.dp_tasks.effort	Total effort for tasks

EVENTS_DATA_SET

Metric name	Metric key	Description
Event Duration	sap.calm.events_data_set.duration	Duration of status events
Event Data Set Count	sap.calm.events_data_set.counter	Count of status events

DP_DEFECTS

Metric name	Metric key	Description
Defect Count	sap.calm.dp_defects.counter	Total number of defects in projects

DP_FEATURES

Metric name	Metric key	Description
Feature Count	sap.calm.dp_features.counter	Total number of features in projects

BSM_ANALYTICS_PROVIDER

Metric name	Metric key	Description
Business Service SLA	sap.calm.bsm_analytics_provider.sla	Service Level Agreement percentage for business services
Business Service SLO	sap.calm.bsm_analytics_provider.slo	Service Level Objective percentage for business services

EVENTS

Metric name	Metric key	Description
Event Count	sap.calm.events.events	Total number of monitoring events
Event Situations	sap.calm.events.eventsituations	Number of event situations detected
Event Total Duration	sap.calm.events.totalduration	Total duration of events
Event Tickets	sap.calm.events.tickets	Number of tickets created from events
Event Alerts	sap.calm.events.alerts	Number of alerts generated from events
Event Mails	sap.calm.events.mails	Number of email notifications sent for events
Event Chat Messages	sap.calm.events.chatmessages	Number of chat messages generated from events
Event Operation Flows	sap.calm.events.operationflows	Number of operation flows triggered by events

SUM_DATAPROVIDER

Metric name	Metric key	Description
SUM Not Available Count	sap.calm.sum_dataprovider.notavailable	Number of synthetic monitoring scenarios not available
SUM Available Count	sap.calm.sum_dataprovider.available	Number of synthetic monitoring scenarios available
SUM Availability Not Rated Count	sap.calm.sum_dataprovider.availabilitynotrated	Number of synthetic monitoring scenarios with availability not rated
SUM Execution Count	sap.calm.sum_dataprovider.executions	Total number of synthetic monitoring executions
SUM Critical Performance Count	sap.calm.sum_dataprovider.criticalperformance	Number of synthetic monitoring scenarios with critical performance
SUM Poor Performance Count	sap.calm.sum_dataprovider.poorperformance	Number of synthetic monitoring scenarios with poor performance
SUM Good Performance Count	sap.calm.sum_dataprovider.goodperformance	Number of synthetic monitoring scenarios with good performance
SUM Performance Not Rated Count	sap.calm.sum_dataprovider.performancenotrated	Number of synthetic monitoring scenarios with performance not rated
SUM Response Time	sap.calm.sum_dataprovider.responsetime	Response time for synthetic monitoring scenarios

DP_REQUIREMENTS

Metric name	Metric key	Description
Requirement Count	sap.calm.dp_requirements.counter	Total number of requirements in projects

Cloud ALM API Metrics

Metric name	Metric key	Description
Total API Requests	sap.calm.totalApiRequests	Total number of API requests made to SAP Cloud ALM
Total Response Size	sap.calm.totalResponseSize	Total size of API responses received from SAP Cloud ALM
Data Provider Execution Time	sap.calm.dpProviderExecutionTime	Time taken to execute the data provider API call
SAP Cloud ALM Service	sap.calm.services	Presence metric emitted once per (service, provider) pair to anchor topology node extraction and edges

DP_QGATES

Metric name	Metric key	Description
Quality Gate Count	sap.calm.dp_qgates.counter	Total number of quality gates
Quality Gate Checklist Count	sap.calm.dp_qgates.checklistcounter	Total number of quality gate checklist items

DP_TESTS

Metric name	Metric key	Description
Test Total	sap.calm.dp_tests.total	Total number of tests executed

DP_RUM_REQUEST_TYPES

Metric name	Metric key	Description
RUM Response Time	sap.calm.dp_rum_request_types.responsetime	Real user monitoring response time for requests
RUM User Count	sap.calm.dp_rum_request_types.users	Number of users making requests
RUM Request Count	sap.calm.dp_rum_request_types.requests	Total number of user requests
RUM OK Status Count	sap.calm.dp_rum_request_types.okstatus	Number of requests with OK status
RUM Warning Status Count	sap.calm.dp_rum_request_types.warningstatus	Number of requests with warning status
RUM Critical Status Count	sap.calm.dp_rum_request_types.criticalstatus	Number of requests with critical status

KPI_HISTORY_TOTALS

Metric name	Metric key	Description
KPI Value	sap.calm.kpi_history_totals.kpivalue	Key Performance Indicator value for business process monitoring

CPI_MESSAGES

Metric name	Metric key	Description
Integration Message Count	sap.calm.cpi_messages.count.gauge	Number of integration messages processed

Feature set metrics

You can enable or disable each feature set independently.

Recommended feature sets

Feature Set	Provider ID	Metrics
Cloud ALM API Metrics	None	Total API requests, response size, data provider execution time
Projects Analytics	`DP_PROJECTS`	Project status
Business Process Monitoring	`KPI_HISTORY_TOTALS`	KPI values by KPI ID, name, and category
Monitoring Events	`EVENTS`	Event count, situations, duration, tickets, alerts, notifications
Status Events	`EVENTS_DATA_SET`	Event duration and count by type and status
Health Monitoring	`HM_ANALYTICS_DP`	Value, limit, usage, OK/warning/critical status counts
Job Monitoring	`DP_JOB_MONITORING`	Executions, runtime, success, warning, aborted, app warning, app error
Defects Analytics	`DP_DEFECTS`	Defect count by project, scope, status, and priority
Features Analytics	`DP_FEATURES`	Feature count by project, scope, requirement, status, and priority
Requirements Analytics	`DP_REQUIREMENTS`	Requirement count by project, status, priority, and approval
Tasks Analytics	`DP_TASKS`	Task count, story points, and effort by type and status
Tests Analytics	`DP_TESTS`	Test totals by project, scope, type, and status
Quality Gates Analytics	`DP_QGATES`	Quality gate count and checklist count by project and status

Optional feature sets

Feature Set	Provider ID	Metrics
Exception Monitoring	`EXM_DATAPROVIDER`	Exception count by service and category
Integration Monitoring (SAP Integration Suite)	`CPI_MESSAGES`	Message count by service, artifact, and status group
Real User Monitoring	`DP_RUM_REQUEST_TYPES`	Response time, user count, request count, and status indicators by request type
Synthetic User Monitoring	`SUM_DATAPROVIDER`	Availability, performance ratings, executions, and response times
Business Services Analytics	`BSM_ANALYTICS_PROVIDER`	SLA and SLO percentages by business service
Configuration & Security Analysis	`CCDB_STORE_DATA`	Changes, stores, items, and notification counts per store

Explore in Dynatrace Hub

Monitor SAP Cloud ALM health, jobs, integrations, and project analytics in Dynatrace with analytics metrics, OTel logs, and Real User Monitoring traces.