@sap/e2e-trace
SAP 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.
Following one business transaction across several SAP components means carrying an identifier through each of them, and in SAP's systems that identifier is the SAP Passport: a hex string in the sap-passport header holding a transactionID, rootContextID, connectionID and connectionCounter that every component is expected to write into its own logs and pass on. This package is the Node.js side of that. Its Passport parses the header, reads the four identifiers, updates the passport with the name of the current component and the connection it is about to open, compacts it for SAP HANA, which limits how large a passport may be, and serialises it back to a hex string for the next request; sent to SAP HANA it travels as the SAP_PASSPORT session variable rather than a header. createDsrMiddleware is the other half, a connect or express middleware placed first in the chain, which writes one Distributed Statistics Record as JSON on standard output for every request that arrives with a passport, carrying the URL, bytes received and sent, response time, transaction ID and user. Neither half starts a trace or ships one anywhere: the passport comes from the client, a browser plugin or a SAPUI5 frontend, the connection ID and counter are the caller's to supply, and the records go wherever the process's output goes.
Facts
Where it sits
Who is behind it
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- Package
- Origin
- By SAP
- Runtime
- Node.js
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Traces, metrics and correlation for a running service
Download
Install
npm add @sap/e2e-traceDerived from the package name. No recipe recorded; the README has the configuration.
README
quoted from @sap/e2e-trace@6.2.2, read@sap/e2e-trace
Node.js package with end to end tracing capabilities.
History
Others providing
Compare all 19 on the Telemetry page →- abap-metrics-providerabap-metrics-providerExposes 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.independent, abapExposes ABAP stack metrics to a monitoring toolfrom ABAP
- 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-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
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-e2e-trace- JSON
- /artifacts/sap-e2e-trace.json
- MCP
- Connecting an agent