elastic-apm-http-client - npm Package Versions

v12.0.0

• Breaking change. The hostname configuration option has been renamed to configuredHostname. As well, the hostname detection has changed to prefer using a FQDN, if available. See the spec. (https://github.com/elastic/apm-agent-nodejs/issues/3310)

• The APM client will send metadata.system.detected_hostname and metadata.system.configured_hostname as appropriate for APM server versions

  =7.4, rather than the now deprecated metadata.system.hostname. See the spec.

v11.4.0

• Add support for pre-registering of partial transactions for AWS Lambda. This adds client.lambdaShouldRegisterTransactions() and client.lambdaRegisterTransaction(transaction, awsRequestId) so the APM agent can register a partial transaction with the Elastic Lambda extension before executing the user's handler. In some error cases (uncaughtException, unhandledRejection, Lambda timeout), the extension can report that transaction when the APM agent is unable. (https://github.com/elastic/apm-agent-nodejs/issues/3136)

v11.3.1

• Tweak logic to only exclude metadata.service.agent.activation_method when the APM server version is known to be 8.7.0 -- i.e. optimistically assume it is a version that is fine. The APM server 8.7.0 issue isn't so severe that we want a fast first serverless function invocation to not send the field. (https://github.com/elastic/apm/pull/783)

v11.3.0

• Ensure metadata.service.agent.activation_method is only sent for APM server version 8.7.1 or later. APM server 8.7.0 included a bug where receiving activation_method is harmful. (https://github.com/elastic/apm-agent-nodejs/issues/3230)

  This change adds the client.supportsActivationMethodField() method.

v11.2.0

• Support a new agentActivationMethod string config var that is added to metadata.service.agent.activation_method. Spec: https://github.com/elastic/apm/blob/main/specs/agents/metadata.md#activation-method

v11.1.0

• Add an extraMetadata config option, which is an object to merge into the built metadata object. This is an alternative to the existing cloudMetadataFetcher and expectExtraMetadata options which provide ways to asynchronously provide metadata. Only one (or zero) of these three options may be used.

v11.0.4

• Update the default serverUrl to "http://127.0.0.1:8200". We no longer use "localhost" to avoid ambiguity if localhost resolves to multiple addresses (e.g. IPv4 and IPv6). APM server only listens on IPv4 by default. (https://github.com/elastic/apm-agent-nodejs/pull/3049)

v11.0.3

• Prevent a possible tight loop in central config fetching. (https://github.com/elastic/apm-agent-nodejs/issues/3029)

v11.0.2

Bad release. Upgrade to 11.0.3.

• Add guards to ensure that a crazy Cache-Control: max-age=... response header cannot accidentally result in inappropriate intervals for fetching central config. The re-fetch delay is clamped to [5 seconds, 1 day]. (https://github.com/elastic/apm-agent-nodejs/issues/2941)

• Improve container-info gathering to support AWS ECS/Fargate environments. (https://github.com/elastic/apm-agent-nodejs/issues/2914)

v11.0.1

• Fix an issue when running in a Lambda function, where a missing or erroring APM Lambda extension could result in apmclient back-off such that (a) the end-of-lambda-invocation signaling (?flushed=true) would not happen and (b) premature "beforeExit" event could result in the Lambda Runtime responding null before the Lambda function could respond (https://github.com/elastic/apm-agent-nodejs/issues/1831).