@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.

Who is behind it

SAPSAPOrganisationMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainer