How Dynatrace supports Node.js applications

Node.js is a server-side framework that's based on the V8 JavaScript engine by Google. Node.js has an asynchonous execution model and is frequently used for gluing or as a proxy tier within enterprise environments.


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)

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, it’s 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 support model, but will support each Node.js version at least half a year longer to give our customers enough time for upgrades.

Node.js Version vendor released Vendor EOL Supported by Dynatrace until Last supported OneAgent Version
0.10 2013-03-11 2016-10-31 October 2017 1.129
0.12 2015-02-06 2016-12-31 October 2017 1.129
4 2015-09-08 2018/04/31 December 2018 1.157
5 2015-10-29 2016-06-30 October 2017 1.129
6 2016-04-26 April 2019 October 2019
7 2016-10-25 2017-06-30 November 2017 1.131
8 2017-05-30 December 2019 June 2020
9 2017-10-01 2018-06-30 December 2018 1.157
10 2018-04-24 April 2021 October 2021

Known Limitations

  • Due to platform limitations of JavaScript and Node.js, code-level-visibility is limited compared to .NET or Java.
  • In conjunction with unsupported third-party modules, context can get lost in asynchronous callbacks. In such cases, please contact support.
  • 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 will be disabled in future. For now, if you run into this issue please disable it in the deep monitoring settings.

Further Reading