Node.js Compatibility Requirements
This product is not supported for your selected
Datadog site. (
).
App and API Protection capabilities
The following App and API Protection capabilities are supported in the Node.js library, for the specified tracer version:
| App and API Protection capability | Minimum Node.js tracer version |
|---|
| HTTP Monitoring | 5.24.0 |
| gRPC Monitoring | not supported |
| GraphQL Monitoring | 5.4.0 |
| Exploit Prevention | 5.30.0 |
| API Security | 5.87.0 |
| Account Takeover Protection | 5.39.0 |
| Runtime Activation | 3.9.0 |
| Runtime Software Composition Analysis (SCA) | 4.1.0 |
| Runtime Code Analysis (IAST) | 5.32.0 |
The minimum tracer version to get all supported App and API Protection capabilities for Node.js is 5.87.0.
The following capabilities are not yet supported: gRPC Monitoring.
Supported deployment types
| Deployment type | Support |
|---|
| Docker | |
| Kubernetes | |
| Amazon ECS | |
| AWS Fargate | |
| AWS Lambda | |
Language and framework compatibility
Node.js Version Support
When the Node.js project drops support for an LTS major release line (when it goes End of Life), support for it is dropped in the next major version of dd-trace.
The last major supporting release line of dd-trace library supports that EOL version of Node.js for at least another year on a maintenance mode basis.
Some issues cannot be solved in dd-trace and instead must be solved in Node.js. When this happens and the Node.js release in question is EOL, it’s not possible to solve the issue without moving to another non-EOL release.
Datadog does not make new releases of dd-trace to provide specific support for non-LTS Node.js major release lines (odd numbered versions).
For the best level of support, always run the latest LTS release of Node.js, and the latest major version of dd-trace. Whatever release line of Node.js you use, also use the latest version of Node.js on that release line, to ensure you have the latest security fixes.
For more information about Node.js release, see the official Node.js documentation.
Operating system support
The following operating systems are officially supported by dd-trace. Any operating system not listed is still likely to work, but with some features missing, for example App and API Protection capabilities, profiling, and runtime metrics. Generally speaking, operating systems that are actively maintained at the time of initial release for a major version are supported.
| Operating System | Architectures | Minimum Versions |
|---|
| Linux (glibc) | arm64, x64 | CentOS 7, Debian 9, RHEL 7, Ubuntu 14.04 |
| Linux (musl) | arm64, x64 | Alpine 3.13 |
| macOS | arm64, x64 | Catalina (10.15) |
| Windows | x64 | Windows 8.1, Windows Server 2012 |
Integrations
Web framework compatibility
- Attacker source HTTP request details
- Tags for the HTTP request (status code, method, etc)
- Distributed Tracing to see attack flows through your applications
Although Threat Protection is available for express >= 4 versions, the blocking of payloads on the body is only supported for applications using either the body-parser or multer libraries.
Data store compatibility
Datastore tracing provides:
- Timing request to response
- Query info (for example, a sanitized query string)
- Error and stacktrace capturing
Threat Protection also works at the HTTP request (input) layer, and so works for all databases by default, even those not listed in the table below.
GraphQL compatibility
User Authentication Frameworks compatibility
