Bump elastic-apm-node from 3.26.0 to 3.31.0

[dependabot]

Bumps elastic-apm-node from 3.26.0 to 3.31.0.

Release notes

Sourced from elastic-apm-node's releases.

v3.31.0

For more information, please see the changelog.

Elastic APM Node.js agent layer ARNs

Region	ARN
af-south-1	arn:aws:lambda:af-south-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
ap-east-1	arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
ap-northeast-1	arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
ap-northeast-2	arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-3-31-0:1
ap-northeast-3	arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-3-31-0:1
ap-south-1	arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
ap-southeast-1	arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
ap-southeast-2	arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-3-31-0:1
ap-southeast-3	arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-3-31-0:1
ca-central-1	arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
eu-central-1	arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
eu-north-1	arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
eu-south-1	arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
eu-west-1	arn:aws:lambda:eu-west-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
eu-west-2	arn:aws:lambda:eu-west-2:267093732750:layer:elastic-apm-node-ver-3-31-0:1
eu-west-3	arn:aws:lambda:eu-west-3:267093732750:layer:elastic-apm-node-ver-3-31-0:1
me-south-1	arn:aws:lambda:me-south-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
sa-east-1	arn:aws:lambda:sa-east-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
us-east-1	arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
us-east-2	arn:aws:lambda:us-east-2:267093732750:layer:elastic-apm-node-ver-3-31-0:1
us-west-1	arn:aws:lambda:us-west-1:267093732750:layer:elastic-apm-node-ver-3-31-0:1
us-west-2	arn:aws:lambda:us-west-2:267093732750:layer:elastic-apm-node-ver-3-31-0:1

v3.30.0

For more information, please see the changelog.

Elastic APM Node.js agent layer ARNs

Region	ARN
af-south-1	arn:aws:lambda:af-south-1:267093732750:layer:elastic-apm-node-ver-3-30-0:1
ap-east-1	arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-3-30-0:1
ap-northeast-1	arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-3-30-0:1
ap-northeast-2	arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-3-30-0:1
ap-northeast-3	arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-3-30-0:1
ap-south-1	arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-3-30-0:1
ap-southeast-1	arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-3-30-0:1
ap-southeast-2	arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-3-30-0:1
ap-southeast-3	arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-3-30-0:1
ca-central-1	arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-3-30-0:1
eu-central-1	arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-3-30-0:1
eu-north-1	arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-3-30-0:1
eu-south-1	arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-3-30-0:1

... (truncated)

Changelog

Sourced from elastic-apm-node's changelog.

==== 3.31.0 2022/03/23

[float] ===== Features

• Add captureBody support for Hapi. ({issues}1905#1905)

• If a SNS or SQS single event trigger to an instrumented Lambda function includes message attributes with the name "traceparent" (and "tracestate"), case-insensitive, then those are used to continue the trace. This was already being done for API Gateway event headers.

[float] ===== Bug fixes

• Fix a bug with Lambda instrumentation where the APM agent would result in an otherwise working Lambda function to respond with null if the Lambda was missing the https://github.com/elastic/apm-aws-lambda[Elastic APM Lambda Extension]. ({issues}2598#2598)

• Fix a bug in Lambda instrumentation in the capturing of SNS and SQS event message attributes. ({issues}2605#2605)

[[release-notes-3.30.0]] ==== 3.30.0 2022/03/10

[float] ===== Breaking changes

• Added a new config option that replaces both and . The latter two are now deprecated, but still supported. If spanStackTraceMinDuration is specified, then any value for the deprecated two options will be ignored.

There is a significant change in default behavior of the APM agent. If none of these configuration options is specified, then the default (spanStackTraceMinDuration: -1) is that stack traces are not collected and reported for any spans. This change in default behavior was made because the CPU performance impact of collecting span stack traces was found to be too high in practice for busy and/or complex applications. This is mentioned in the "Breaking changes" section to highlight the change, but it is not considered breaking in general. The impact is that the "Stack Trace" tab in the "Span details" view in the Kibana APM app will be empty. This was already the case for some spans based on span duration. ({pull}2565#2565)

• Implement the explicit signaling of Lambda invocation completion to the Elastic AWS Lambda Extension. This improves data flushing in a Lambda environment to ensure tracing data is only sent when the Lambda is active.

... (truncated)

Commits

• 76bc074 3.31.0 (#2620)
• 37d7d2e feat: add 'captureBody' support for Hapi (#2618)
• 301744a synchronize json schema specs (#2616)
• 170e411 test: use newer ubuntu for node.js edge tests for GLIBC_2.28 req (#2613)
• 96559d8 fix: if Lambda extension is down, agent eventually causes null function respo...
• 9f4b07b feat: use trace-context "headers" in SNS and SQS single event message attribu...
• d2b4d4a ci: enable tags and run the release stage only for tags (#2609)
• 487f696 3.30.0 (#2607)
• 5a8975e feat: improves Lambda data flushing and extension signaling (#2586)
• a0355c0 feat: capture faas.name and faas.version for Lambda (#2599)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #43.