Dynatrace provides extensive Node.js monitoring capabilities:
- Heap and process metrics
- Heap dumps
- CPU sampling (see known limitations)
- Event loop metrics
- Insights into inbound and outbound HTTP calls
- Dedicated support for a variety of databases (includes query capture)
- Capturing OpenTelemetry traces
- OneAgent SDK for custom tracing
See our supported technologies matrix for details about supported technologies that will be used in conjunction with Node.js.
Support & desupport
Node.js follows an LTS release model.
Each odd-numbered version reaches EOL shortly after each new even-numbered version is released. Each even-numbered version eventually becomes an LTS release. For enterprise production environments, we recommended that you stick to LTS releases.
Whenever a new Node.js major version (even or uneven) is released, we add support for that version.
Dynatrace will follow this support model, but will support each Node.js version at least half a year longer to give our customers time for upgrades.
|Node.js version||Vendor released||Vendor End of life||Supported by Dynatrace until||First supported Dynatrace OneAgent version||Last supported Dynatrace OneAgent version|
In conjunction with unsupported third-party modules, context can be lost in asynchronous callbacks. In such cases, please contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
Using the NPM module esm in variant 1 for packages might result in reduced visibility (especially if used for the main application script). It's preferable to use variant 2 to preload
-rcommand line option.
There is currently only limited support for ECMAScript modules (aka "ES6 modules"):
If the main script file itself is an ECMAScript module OneAgent version 1.219+ with Agent preloading enabled is needed for the OneAgent to be injected into the Node.js process.
Instrumentation of ES6 modules is currently not available. This limits support for
kafkajsin case the user defined entrypoint for the KafkaJs sensor is inside an ES6 module.
Webpack bundles all modules into a single file by default. OneAgent is unable to instrument bundled modules. To work around this limitation all modules which need to be instrumented by the OneAgent (e.g. express, mongodb, pg,…) have to be externalized in the webpack configuration. See webpack Externals documentation for details.
Ambient Sampling limitations for certain OneAgent versions:
Google V8 is affected by a series of memory and CPU overhead issues, which is a blocker for production-level background CPU profiling:
Therefore, CPU profiling (ambient sampling) is not enabled by default for all OneAgent versions:
Ambient sampling is enabled by default as of OneAgent version 1.181
As of OneAgent version 1.181 the above limitations have been resolved by not using v8 CpuProfiler for Ambient Sampling. Ambient Sampling is fully available on all supported platforms and all supported Node.js versions without any restrictions.
Ambient sampling is disabled by default for OneAgent versions 1.157 up to 1.179
On Linux ambient sampling can be enabled for the following Node.js versions:
- Node.js version 6
- Node.js versions ^8.9.4 (8.9.4 <= node.js < 9.0.0)
- Node.js version 9.3.0 or later
On Windows ambient sampling is disabled for these OneAgent versions, because it would cause 100% CPU usage for one CPU.
OneAgent records a log entry for each unsupported version it detects:
AmbientSampling: <unsupported platform> / <node version>