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 for dd-trace is available on these webpages:
- Tracing Node.js Applications - most project documentation, including setup instructions
- Configuring the NodeJS 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 | Status | Initial Release | End of Life |
|---|---|---|---|---|---|
v1 |
 |
>= v12 |
End of Life | 2021-07-13 | 2022-02-25 |
v2 |
 |
>= v12 |
End of Life | 2022-01-28 | 2023-08-15 |
v3 |
 |
>= v14 |
Maintenance | 2022-08-15 | 2024-05-15 |
v4 |
 |
>= v16 |
Maintenance | 2023-05-12 | 2025-01-11 |
v5 |
 |
>= v18 |
Current | 2024-01-11 | Unknown |
We currently maintain three release lines, namely v5, v4 and v3.
Features and bug fixes that are merged are released to the v5 line and, if appropriate, also the v4 & v3 line.
For any new projects it is recommended to use the v5 release line:
$ npm install dd-trace
$ yarn add dd-traceHowever, existing projects that already use the v4 & v3 release line, or projects that need to support EOL versions of Node.js, may continue to use these release lines.
This is done by specifying the version when installing the package.
$ npm install dd-trace@4
$ yarn add dd-trace@4Any 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 the NodeJS Compatibility Requirements page.
Changes associated with each individual release are documented on the GitHub Releases screen.
Please read the CONTRIBUTING.md document before contributing to this open source project.
Warning
ESM support has been temporarily disabled starting from Node 20 as significant changes are in progress.
ESM support is currently in the experimental stages, while CJS has been supported
since inception. This means that code loaded using require() should work fine
but code loaded using import might not always work.
Use the following command to enable experimental ESM support with your application:
Node.js < v20.6
node --loader dd-trace/loader-hook.mjs entrypoint.jsNode.js >= v20.6
node --import dd-trace/register.js entrypoint.jsNote 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 the dd-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 on bundling and dd-trace. It includes information on how to use our ESBuild plugin and includes caveats for other bundlers.
Please refer to the SECURITY.md document if you have found a security issue.