Bump elastic-apm-node from 3.26.0 to 3.27.0

[dependabot]

Bumps elastic-apm-node from 3.26.0 to 3.27.0.

Changelog

Sourced from elastic-apm-node's changelog.

==== 3.27.0 2022/01/17

[float] ===== Features

• Add support for express-graphql 0.10.0 - 0.12.0 inclusive. ({pull}2511#2511)

[float] ===== Bug fixes

• Fix an issue where the agent's async task tracking could cause the user's application to use too much memory. In cases where an application is under sustained load and is running in a memory constrained container, this looked like a memory leak.

This high memory usage could happen when application code starts async tasks (e.g. Promises, setTimeouts, async I/O) that outlive the APM Transaction (typically an HTTP request handler). The agent's async task tracking keeps a reference to the APM Transaction (and any APM Spans) until the async task ends, thus extending the lifetime of those APM objects and the references they hold -- in particular, HTTP request and response objects. This could lead to higher memory usage. + With this change, those references are removed when APM Transactions and Spans are ended, and agent memory usage is now the same as what it was before v3.24.0 when this issue was introduced. ({pull}2528#2528, {issues}2489#2489)

• Fixes for run context handling for 'graphql' instrumentation. ({issues}2430#2430)

• Fixes for run context handling for DynamoDB instrumentation ('aws-sdk' package) so that a span created after an AWS client command (in the same tick, in the command callback, or promise) is not a child of the automatic AWS span. This change also ensures captured errors from failing client commands are a child of the AWS span. ({issues}2430#2430)

• Fixes for run context handling for 'pg' instrumentation. ({issues}2430#2430)

• Fixes for run context handling for 'mongodb' instrumentation. ({issues}2512#2512)

[[release-notes-3.26.0]]

Commits

• cba071c 3.27.0 (#2532)
• dcf6e39 perf: reduce memory retained by async tasks that outlive their transaction/sp...
• 6acaaa0 tests: fix test failure due to os.freemem() behaviour change in node v18 (#2530)
• 7d2e759 fix: ensure correct run context for 'mongodb' instrumentation (#2512)
• 8d8d3c9 feat: support express-graphql 0.10.0 - 0.12.0 (#2511)
• 7a2a312 fix: ensure correct run context for 'graphql' instrumentation (#2509)
• f8f6f78 fix: ensure correct run-context for pg instrumentation (#2506)
• 291be94 ci: avoid retagging official docker node images (#2522)
• 435516a synchronize json schema specs (#2523)
• ae26f6d ci: update ITs main (#2520)
• 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 #34.