Upgrade to v3.x
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. The Elastic APM Node.js agent enables you to trace the execution of operations in your Node.js applications, sending performance metrics and errors to the Elastic APM Server. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless Observability
Generally available
Stack
Generally available
APM Agent Node.js
Generally available
The following is a guide on upgrading your Node.js agent from version 2.x to version 3.x.
Version 3.0.0 of the Node.js agent supports Node.js v8 (from v8.6.0 and onwards), v10, and v12.
The disableInstrumentations config option now behaves differently if given the values http and/or https. Previously this would disable tracing of incoming and outgoing requests. Now this config option only deals with outgoing requests. To disable tracing of incoming http(s) requests, use the new instrumentIncomingHTTPRequests config option.
It’s now possible to make use of manual instrumention while the instrument config option is set to false. This means that calls to for instance apm.startTransaction() or apm.startSpan() will produce transactions and spans even if instrument is set to false.
The type associated with transactions and spans is no longer dot-separated. Instead the type property has been split into three distinct properties: type, subtype, and action. This has resulted in changes to the following API’s:
apm.startTransaction(): Function arguments changedapm.startSpan(): Function arguments changedtransaction.startSpan(): Function arguments changedtransaction.type: String format changedspan.type: String format changed
The following deprecated API’s has been removed:
apm.setTag(): Replaced byapm.setLabel()apm.addTags(): Replaced byapm.addLabels()transaction.setTag(): Replaced bytransaction.setLabel()transaction.addTags(): Replaced bytransaction.addLabels()span.setTag(): Replaced byspan.setLabel()span.addTags(): Replaced byspan.addLabels()
When instrumenting a GraphQL server that is run by apollo-server-express the Transaction type is now graphql instead of request.
All Spans whose type was previously ext is now external.