chore(deps): bump elastic-apm-node from 4.4.1 to 4.5.4

Bumps elastic-apm-node from 4.4.1 to 4.5.4.

Release notes

Sourced from elastic-apm-node's releases.

v4.5.4

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-4-5-4:1

ap-east-1 arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

ap-northeast-1 arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

ap-northeast-2 arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-4-5-4:1

ap-northeast-3 arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-4-5-4:1

ap-south-1 arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

ap-southeast-1 arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

ap-southeast-2 arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-4-5-4:1

ap-southeast-3 arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-4-5-4:1

ca-central-1 arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

eu-central-1 arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

eu-north-1 arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

eu-south-1 arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

eu-west-1 arn:aws:lambda:eu-west-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

eu-west-2 arn:aws:lambda:eu-west-2:267093732750:layer:elastic-apm-node-ver-4-5-4:1

eu-west-3 arn:aws:lambda:eu-west-3:267093732750:layer:elastic-apm-node-ver-4-5-4:1

me-south-1 arn:aws:lambda:me-south-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

sa-east-1 arn:aws:lambda:sa-east-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

us-east-1 arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

us-east-2 arn:aws:lambda:us-east-2:267093732750:layer:elastic-apm-node-ver-4-5-4:1

us-west-1 arn:aws:lambda:us-west-1:267093732750:layer:elastic-apm-node-ver-4-5-4:1

us-west-2 arn:aws:lambda:us-west-2:267093732750:layer:elastic-apm-node-ver-4-5-4:1

v4.5.3

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-4-5-3:1

ap-east-1 arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-4-5-3:1

ap-northeast-1 arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-4-5-3:1

ap-northeast-2 arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-4-5-3:1

ap-northeast-3 arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-4-5-3:1

ap-south-1 arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-4-5-3:1

ap-southeast-1 arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-4-5-3:1

ap-southeast-2 arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-4-5-3:1

ap-southeast-3 arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-4-5-3:1

ca-central-1 arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-4-5-3:1

eu-central-1 arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-4-5-3:1

eu-north-1 arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-4-5-3:1

eu-south-1 arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-4-5-3:1

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

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

... (truncated)

Changelog

Sourced from elastic-apm-node's changelog.

==== 4.5.4 - 2024/05/13

[float] ===== Bug fixes

Change how the "cookie" HTTP request header is represented in APM transaction data to avoid a rare, but possible, intake bug where the transaction could be rejected due to a mapping conflict.

Before this change a Cookie: foo=bar; sessionid=42 HTTP request header would be represented in the transaction document in Elasticsearch with these document fields (the example assumes matches "sessionid", as it does by default): + [source]

http.request.headers.cookie: "[REDACTED]" ... http.request.cookies.foo: "bar" http.request.cookies.sessionid: "[REDACTED]"

After this change it is represented as: + [source]

http.request.headers.cookie: "foo=bar; sessionid=REDACTED"

In other words, http.request.cookies are no longer separated out. ({issues}4006#4006)

[[release-notes-4.5.3]] ==== 4.5.3 - 2024/04/23

[float] ===== Bug fixes

Fix message handling for tombstone messages in kafkajs instrumentation. ({pull}3985#3985)

[[release-notes-4.5.2]] ==== 4.5.2 - 2024/04/12

[float] ===== Bug fixes

Fix path resolution for requests that contain invalid characters in its

... (truncated)

Commits

f1fea2e release 4.5.4 (#4018)
89852de fix: change how 'cookie' header is represented in trans to avoid possible map...
041109a ci: use docker/metadata-action to gather tags/labels (#3998)
b76a83a chore(deps): bump @opentelemetry/exporter-prometheus (#4016)
571b362 chore(deps): bump @opentelemetry/sdk-metrics to 1.24.1 in test fixtures (#4015)
30900c1 chore(deps): bump @opentelemetry/sdk-metrics from 1.24.0 to 1.24.1 (#4014)
d1cb197 chore(deps-dev): bump azure-functions-core-tools (#4017)
7637b10 chore(deps-dev): bump undici from 6.15.0 to 6.16.1 (#4013)
4e40b8c chore(deps-dev): bump fastify from 4.26.2 to 4.27.0 (#4012)
eedba5a chore(deps): bump pino from 8.17.1 to 8.21.0 (#4011)
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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

frmscoe / tms-service

chore(deps): bump elastic-apm-node from 4.4.1 to 4.5.4 #158

v4.5.4

Elastic APM Node.js agent layer ARNs

v4.5.3

Elastic APM Node.js agent layer ARNs

Before this change a `Cookie: foo=bar; sessionid=42` HTTP request header would be represented in the transaction document in Elasticsearch with these document fields (the example assumes matches "sessionid", as it does by default): + [source]

http.request.headers.cookie: "[REDACTED]" ... http.request.cookies.foo: "bar" http.request.cookies.sessionid: "[REDACTED]"

After this change it is represented as: + [source]

http.request.headers.cookie: "foo=bar; sessionid=REDACTED"

Quality Gate passed

frmscoe / tms-service

chore(deps): bump elastic-apm-node from 4.4.1 to 4.5.4 #158

v4.5.4

Elastic APM Node.js agent layer ARNs

v4.5.3

Elastic APM Node.js agent layer ARNs

Before this change a Cookie: foo=bar; sessionid=42 HTTP request header would be represented in the transaction document in Elasticsearch with these document fields (the example assumes matches "sessionid", as it does by default): + [source]

http.request.headers.cookie: "[REDACTED]" ... http.request.cookies.foo: "bar" http.request.cookies.sessionid: "[REDACTED]"

After this change it is represented as: + [source]

http.request.headers.cookie: "foo=bar; sessionid=REDACTED"

Quality Gate passed

Before this change a `Cookie: foo=bar; sessionid=42` HTTP request header would be represented in the transaction document in Elasticsearch with these document fields (the example assumes matches "sessionid", as it does by default): + [source]