Repository files navigation

dd-trace is an npm package that you can install in your Node.js application to capture APM (Application Performance Monitoring) data. In Datadog terminology this library is called a Tracer. This data is then sent off to a process which collects and aggregates the data, called an Agent. Finally the data is sent off to the Datadog servers where it's stored and made available for querying in a myriad of ways, such as displaying in a dashboard or triggering alerts.

Most of the documentation fordd-trace is available on these webpages:

• Tracing Node.js Applications - most project documentation, including setup instructions
• Configuring the Node.js Tracing Library - environment variables and config options
• API Documentation - method signatures, plugin list, and some usage examples
• APM Terms and Concepts - a glossary of concepts applicable across all languages

Release Line	Latest Version	Node.js	SSI	K8s Injection	Status	Initial Release	End of Life
v1		>= v12	NO	NO	EOL	2021-07-13	2022-02-25
v2		>= v12	NO	NO	EOL	2022-01-28	2023-08-15
v3		>= v14	NO	YES	EOL	2022-08-15	2024-05-15
v4		>= v16	YES	YES	EOL	2023-05-12	2025-01-11
v5		>= v18	YES	YES	Current	2024-01-11	Unknown

• EOL = End-of-life
• SSI = Single-Step Install

We currently maintain one release line, namelyv5.

For any new projects it is recommended to use thev5 release line:

$ npm install dd-trace$ yarn add dd-trace

Existing projects that need to use EOL versions of Node.js may continue to use these older release lines.This is done by specifying the version when installing the package.

$ npm install dd-trace@4# or whatever version you need$ yarn add dd-trace@4# or whatever version you need

Note, however, that the end-of-life release lines are no longer maintained and will not receive updates.

Any backwards-breaking functionality that is introduced into the library will result in an increase of the major version of the library and therefore a new release line.Such releases are kept to a minimum to reduce the pain of upgrading the library.

When a new release line is introduced the previous release line then enters maintenance mode where it will receive updates for the next year.Once that year is up the release line enters End of Life and will not receive new updates.The library also follows the Node.js LTS lifecycle wherein new release lines drop compatibility with Node.js versions that reach end-of-life (with the maintenance release line still receiving updates for a year).

For more information about library versioning and compatibility, see theNode.js Compatibility Requirements page.

Changes associated with each individual release are documented on theGitHub Releases screen.

Please read theCONTRIBUTING.md document before contributing to this open source project.

ESM support requires anadditional command line argument when starting the Node.js process.For more information, see thesection on ESM support in the Node.js tracer documentation.

Note that there is a separate Lambda project,datadog-lambda-js, that is responsible for enabling metrics and distributed tracing when your application runs on Lambda.That project does depend on thedd-trace package but also adds a lot of Lambda-related niceties.If you find any issues specific to Lambda integrations then the issues may get solved quicker if they're added to that repository.That said, even if your application runs on Lambda, any core instrumentation issues not related to Lambda itself may be better served by opening an issue in this repository.Regardless of where you open the issue, someone at Datadog will try to help.

If you would like to trace your bundled application then please read this page onbundling and dd-trace. It includes information on how to use our ESBuild plugin and includes caveats for other bundlers.

Please refer to theSECURITY.md document if you have found a security issue.

Please refer to theNode.js Custom Instrumentation using OpenTelemetry API document. It includes information on how to use the OpenTelemetry API with dd-trace-js.