abap-metrics-provider
Exposes predefined or custom metrics from an ABAP stack to a monitoring tool of choice, through a provider and a scraper component that reuse the metrics format of abap-prometheus.
Exposes predefined or custom metrics from an ABAP stack to a monitoring tool of choice, split into a provider component and a scraper component, each documented with its own class diagram. It is based on abap-prometheus, reusing that client's metrics format rather than building one from scratch. Statement compatibility for the code is tracked through abaplintabaplintStatic analysis for ABAP that runs outside a system on serialised source in a repository, so ABAP checks run in a pull request and in CI before the code ever reaches a system.community org, abap, and a video playlist documents the setup.
Facts
Where it sits
Who is behind it
In the atlas: maintains 2@abap-observability-toolsmaintainerMax MilazzoContributes to this
In the atlas: contributes to 2@GoalaJohannes KoningsContributes to this
In the atlas: contributes to 7@JohannesKoningsLars HvamContributes to this
In the atlas: maintains 13, contributes to 92, wrote 1@larshpThoralf HänselContributes to this
In the atlas: contributes to 2@ThoralfHaensel4 contributors
Before choosing this
Signals
RepositoryArchivedThe declared repository is archived
GitHub reports the repository as archived. The package may remain installable, but its source is no longer open for normal maintenance.
What it declares
Every artifact
- Type
- App
- Origin
- Independently maintained
As an app
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Traces, metrics and correlation for a running service
Download
README
quoted from abap-observability-tools/abap-metrics-provider under MIT, readabap-metrics-provider
compatibility
architecture
component diagramm

class diagramm
provider

scraper

documentation
local tests
based on
History
Changed
Notes
Changes
Changed 76
Notes
Changes
- release-drafter added @JohannesKonings (#159)
- github action automatic changelog updated added @JohannesKonings (#158)
- readme influxdb util curl drop data added @JohannesKonings (#156)
- metrics delete prog depending on timestamp added @JohannesKonings (#155)
- conditional deletion of metrics in metric store @JohannesKonings (#154)
- abaplint rules disabled and some little fixes @JohannesKonings (#149)
- youtubevideo link in readme added @JohannesKonings (#148)
- Link to abaplint converter UML added @JohannesKonings (#147)
- Link to abaplint collector UML added @JohannesKonings (#146)
- disabled some abaplint rules @JohannesKonings (#145)
- abaplint.yml deleted @JohannesKonings (#144)
- snyk badge removed @JohannesKonings (#142)
- pull request template created @JohannesKonings (#141)
- auth docu added @JohannesKonings (#139)
- auth fix confusion scraper with provider @JohannesKonings (#138)
- Authorithy checks added @JohannesKonings (#135)
- Batch input metrics @Goala (#134)
- abaplint update and fixes @JohannesKonings (#131)
- http json converter escaping and valid empty json conversion added @JohannesKonings (#130)
- dashboards updated to new naming convention @JohannesKonings (#129)
- doc updates @JohannesKonings (#128)
- metric name for inbound and outbound @JohannesKonings (#126)
- collector for queued RFCs added @JohannesKonings (#121)
- Add batch input metrics @Goala (#124)
- clear table after append to total table @JohannesKonings (#123)
- initialisation of metrics added @JohannesKonings (#120)
- Add bal msgty metric @Goala (#114)
- collector SM50 work processes added @JohannesKonings (#112)
- Add dashboard example @Goala (#110)
- example dashboard for transactional RFCs added @JohannesKonings (#106)
- Transport states @JohannesKonings (#105)
- customzing standard recording routine added @JohannesKonings (#104)
- Update packagejson @Goala (#102)
- update actions to new head branch name @larshp (#100)
- Add bal collector @Goala (#99)
- Init metrics @Goala (#98)
- Update links and readme @Goala (#97)
- content type from converter to scrapper added @JohannesKonings (#94)
- contribution file added @JohannesKonings (#93)
- basic setup for prometheus local-test added @JohannesKonings (#92)
- changed SM58 collector implmentation @JohannesKonings (#87)
- pass metrics last run to collector @JohannesKonings (#89)
- Sm58 collector @JohannesKonings (#85)
- compatibility section added @JohannesKonings (#80)
- use links to abap class instead of source code examples in docs @ThoralfHaensel (#78)
- fix class description for prometheus converter @ThoralfHaensel (#79)
- added docs for SQL monitor @ThoralfHaensel (#76)
- Update metrics keys @ThoralfHaensel (#74)
- Added new collector for SQL monitor @ThoralfHaensel (#72)
- to upper case for scenario in scraper removed @JohannesKonings (#69)
- subpackage prefix changed to Z @JohannesKonings (#66)
- scenario added to converter @JohannesKonings (#64)
- customizing with scenario and group id @JohannesKonings (#62)
- scraper architecture extended @JohannesKonings (#60)
- new packages and object reassigned @JohannesKonings (#59)
- Fix type of scenario. @ThoralfHaensel (#58)
- prometheus converter implementation added @JohannesKonings (#57)
- Pass current run to collectors @Goala (#52)
- Refactor time date passing @Goala (#49)
- metric convention for influxdb datasource @JohannesKonings (#47)
- Dashboard examples for datasource influxdb @JohannesKonings (#46)
- collector for workloads (ST03N) added @JohannesKonings (#45)
- Scrapper scenario @JohannesKonings (#43)
- Extend zamp_store @Goala (#42)
- Collector jobs @JohannesKonings (#41)
- Collector runtime errors @JohannesKonings (#38)
- Reassign packages @Goala (#36)
- Customize metrics convertion @JohannesKonings (#30)
- docker and configurations for local tests added @JohannesKonings (#28)
- Scenario in scrapper @JohannesKonings (#27)
- customizing wrapper created @JohannesKonings (#22)
- view cluster for configuration amp created @JohannesKonings (#21)
- architectur png generated and headings added @JohannesKonings (#19)
- class UML typo fixed @JohannesKonings (#18)
- added component customizing in architecture UML @JohannesKonings (#17)
- change language from D to E @JohannesKonings (#14)
Others providing
Compare all 19 on the Telemetry page →- admin-cockpitadmin-cockpitAn abap2UI5 app that shows usage, errors, response times, the draft table and a security traffic light of an abap2UI5 installation.community org, abapUsage, error and response-time monitor for abap2UI5from ABAP
- SAP Cloud LoggingSAP Cloud LoggingAn instance-based observability service built on OpenSearch that stores and analyses logs, metrics and traces from Cloud Foundry, Kyma, Kubernetes and other runtime environments.sap official, btpOpenSearch-based store for logs, metrics and tracesfrom BTP/BAIP
- Agent Activation for Dynatrace Service for SAP BTPAgent Activation for Dynatrace Service for SAP BTPInjects the Dynatrace agent into Java applications on SAP BTP, so their metrics, events and end-to-end traces go to a Dynatrace SaaS monitoring environment the customer already runs.sap official, btpInjects the Dynatrace agent into Java applications on SAP BTPfrom BTP/BAIP
- SAP Monitoring Service for SAP BTPSAP Monitoring Service for SAP BTPMetrics, availability and JMX checks, and email or webhook alerts for Java, HTML5 and SAP HANA XS applications and database systems, in Neo regions of SAP BTP.sap official, btpMetrics, availability checks and alerts for apps in Neo regionsfrom BTP/BAIP
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versionsfrom CAP
- @cap-js-community/business-metrics@cap-js-community/business-metricsAn extension of @cap-js/telemetry that turns two CDS annotations into business metrics, a counter on an entity event or action and a gauge on numeric fields.community org, capBusiness-level metrics from CDS annotations via @cap-js/telemetryfrom CAP
- @cap-js/telemetry@cap-js/telemetryAutomatic OpenTelemetry instrumentation for CAP Node.js services and their database calls, exported as traces and metrics to the console, SAP Cloud Logging, Dynatrace, Jaeger or an OTLP endpoint.sap official, capOpenTelemetry instrumentation for CAP servicesfrom CAP
- cds-cachingcds-cachingA caching plugin for CAP covering queries, requests, function results and remote service responses, through a read-through API or @cache annotations, with HCQL and MCP support.independent, capCAP caching plugin for query results and remote service responsesfrom CAP
- cap-mcp-guardcap-mcp-guardA CDS plugin — the trust layer for AI agents accessing SAP CAP business data — request interception, policy enforcement, field masking/pseudonymization, and OpenTelemetry-native observability for MCP-enabled applications.independent, capPolicy enforcement and field masking for MCP-enabled CAP appsfrom CAP
- abap-opentelemetryabap-opentelemetryAn ABAP library that serialises OpenTelemetry Protocol (OTLP) traces, metrics and logs for sending to a collector, documenting the HTTP request to Elastic 8.8 and later.independent, abapOTLP serialisation of traces, metrics and logs in ABAPfrom ABAP
- abap-prometheusabap-prometheusA Prometheus client for ABAP, the client side of a Prometheus setup, cloned or imported into the system with abapGit.independent, abapPrometheus client for ABAP, installed with abapGitfrom ABAP
- @sanjay-sde/cap-js-log-control@sanjay-sde/cap-js-log-controlA CAP plugin for controlling CDS logger verbosity and OpenTelemetry DiagLogger noise, reducing log clutter so that real errors surface.independent, capCAP plugin controlling CDS logger and OpenTelemetry log verbosityfrom CAP
- @sap/e2e-trace@sap/e2e-traceSAP Passport handling for a Node.js component: it reads the identifiers a request arrives with, updates them for the next system, and writes a statistics record per request to standard output.sap official, btpSAP Passport handling for Node.js componentsfrom BTP/BAIP
- @sap-ux/telemetry@sap-ux/telemetryLibrary for sending usage telemetry datasap official, capLibrary for sending usage telemetry datafrom CAP
- @saptools/cf-metrics@saptools/cf-metricsA read-only command line that queries the container and OpenTelemetry metrics SAP Cloud Logging has ingested for Cloud Foundry apps, as history over a time range, a ranking across apps or a live watch.independent, btpRead-only query tool for metrics in SAP Cloud Loggingfrom BTP/BAIP
- @saptools/cf-otel@saptools/cf-otelA read-only command line that queries the OpenTelemetry trace spans SAP Cloud Logging has already ingested and ranks the spans of a trace by self-time.independent, btpRead-only query tool for OpenTelemetry spans in SAP Cloud Loggingfrom BTP/BAIP
- cap-ui-telemetrycap-ui-telemetryUI5 frontend performance (FESR) and client error capture for CAP, written as cds.log records and forwarded to SAP Cloud Logging, rather than as OpenTelemetry spans.independent, capUI5 frontend performance and error capture for CAPfrom CAP
- opentelemetry-cdsopentelemetry-cdsopentelemetry support for CDS nodejs runtimeindependent, capOpenTelemetry support for the CDS Node.js runtimefrom CAP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
abaplint
History in the atlas
- First seen.
For your agent
- Ref
artifact:abap-observability-tools-abap-metrics-provider- JSON
- /artifacts/abap-observability-tools-abap-metrics-provider.json
- MCP
- Connecting an agent