Telemetry
In ABAP telemetry is exported from the system to a tool outside it: metrics exposed for Prometheus to scrape, or traces, metrics and logs serialised as OTLP and posted to a backend such as Elastic.
Overview
SAP Cloud ALM health monitoring collects technical metrics from ABAP systems on a regular basis, among them work process usage, response time and ABAP runtime errors, and calculates the health of the monitored system from them.
Not covered: At SAP Cloud ALM. The metrics are the ones SAP defines and they are read in SAP's tool; exposing them to Prometheus, or sending traces and logs as OpenTelemetry to another backend, is written on top.
The core side is SAP Cloud ALMSAP Cloud ALMSAP's application lifecycle management product, run by SAP as a service: implementation projects with their tasks, requirements, features, documents and test management, and the operations side of a landscape. For the things here it is the system a server reads over the published Cloud ALM APIs, on behalf of an agent.. The community and independent tools expose metrics to Prometheus, send OpenTelemetry data to a backend, or record the usage and response times of an abap2UI5abap2UI5One ABAP class implementing z2ui5_if_app is the whole app: the browser loads a generic UI5 shell once, and every interaction after that is an HTTP roundtrip back into ABAP.community org, abap installation.
Artifacts
Content
Details
Coverage
For your agent
- Ref
capability:telemetry- JSON
- /capabilities/telemetry.json
- MCP
- Connecting an agent