Supported technologies

The Elastic APM Node.js Agent automatically instruments various APIs in Node.js core and third-party frameworks and packages. This page lists all supported technologies and version ranges.

Support for the Elastic APM Node.js agent follows the support schedule of Node.js itself to the end-of-life period of each version after its maintenance term. Versions of Node.js past their end-of-life date are not supported.

APM agent 4.x releases work with Node.js versions 14.17.0 and later. APM agent 3.x maintenance releases work with Node.js versions 8.6 and later. We will only break support for older Node.js versions with a major version release of the APM agent.

Beginning with version v3.48.0, the Elastic APM Node.js agent includes limited and experimental support for instrumenting ECMAScript module imports, i.e. modules that are loaded via import ... statements and import('...') (dynamic import). See the ECMAScript module support document for details.

Note: If you are using TypeScript or JavaScript that is compiled/translated/transpiled to CommonJS-using JavaScript via tools like Babel, Webpack, esbuild, etc., then using import ... in your source code is fine. To ensure your compiler is generating JS that uses CommonJS imports, use the following settings:

This agent is compatible with APM Server v6.6 and above.

Though you can use Elastic APM with any Node.js framework, we automate a few things for the most popular Node.js modules. These are the frameworks that we officially support:

The Node.js Elastic APM agent supports usage of the OpenTelemetry Tracing API via its OpenTelemetry bridge. As well, it instruments the OpenTelemetry Metrics API and Metrics SDK to allow usage of the OpenTelemetry Metrics API.

By default transactions are named based on their matched HTTP route if the framework used is listed above. These modules override that behavior to give better insights into specialized HTTP servers:

The Node.js agent will automatically instrument the following modules to give you detailed performance metrics:

The APM agent can be configured to capture span stack traces, to show where in your code a span (e.g. for a database query) was initiated.

Given the async nature of Node.js, it’s not possible for the APM agent to see further back than the last async boundary. Modules that happen to have an async boundary between a call from your application code and the action that leads to an APM span will limit the utility of these span stack traces.

The modules listed below are those that the APM agent instruments to provide more useful span stack traces — ones that point to your application code — when enabled.

If you don’t see your own code in spans, please create a new topic in the Elastic APM discuss forum and include information about your dependencies.

The Elastic APM agent monitors async operations in your Node.js application to maintain awareness of which request is the active request at any given time. Certain modules can interfere with this monitoring if not handled properly.

Below is a list of modules known to cause issues with this monitoring. The versions listed are the versions we support. If you use an unsupported version you might experience missing spans. This does not impact the stability of your application in any way - only the collected metrics.

If you do experience missing spans in your performance metrics, please create a new topic in the Elastic APM discuss forum and include information about your dependencies and what data is missing.