v11.126.0

Important

This version imports dd-trace-js v5.56.0

# AWS Commercial
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:126
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:126
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:126

# AWS GovCloud
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:126
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:126
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:126

What's Changed

• (fix): http.url tag to include protocol by @duncanista in #656
• (fix): Typescript Timeouts when Lambda handler returns undefined by @nhulston in #661

Full Changelog: v10.125.0...v11.126.0

v11.125.0

Important

This version imports dd-trace-js v5.51.0

Warning

This version contains a breaking change

Metrics sent by users with: (1) No extension, (2) no forwarder, and (3) with FIPS mode enabled will not be sent because the metrics API may not be FIPS compliant. Any user with the extension, forwarder, or FIPS disabled will not be affected.

# AWS Commercial
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:125
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:125
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:125

# AWS GovCloud
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:125
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:125
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:125

What's Changed

• (chore): Add ap-southeast-7 and mx-central-1 regions by @nhulston in #646
• Fix span pointer environment variables by @nhulston in DataDog/dd-trace-js#5546
• Extract trace context from ALB multiValueHeaders by @nhulston in #647
• Implement dogstatsd, add timestamp support, fix flushing by @nhulston in #648
• [breaking] FIPS compliant metrics + secrets management by @nhulston in #649
• Fix SignatureDoesNotMatch error when SecretsManager enabled by @nhulston in #650
• (chore): Bump tracer to v5.51.0 by @nhulston in #652
• v11.125.0 by @nhulston in #651

Full Changelog: v10.124.0...v11.125.0

v10.124.0

Important

dd-trace-js version is v5.44.0

# AWS Commercial
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:124
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:124
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:124

# AWS GovCloud
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:124
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:124
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:124

What's Changed

• chore: upgrade tracer to v5.42.0 by @duncanista in #640
• Extract status code when returned as string by @nhulston in #642
• Sles 2151 fix race condition flush by @alexgallotta in #643
• bump dd-trace to 5.44.0 by @alexgallotta in #644
• v10.124.0 by @alexgallotta in #645

New Contributors

• @alexgallotta made their first contribution in #643

Full Changelog: v10.123.0...v10.124.0

v10.123.0

Important

dd-trace-js version is v5.41.1

# AWS Commercial
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:123
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:123
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:123

# AWS GovCloud
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:123
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:123
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:123

What's Changed

• Use FIPs endpoint for SecretManager when in Govcloud region by @nhulston in #634
• Use FIPs endpoint for KMS when in Govcloud region by @nhulston in #635
• chore: upgrade tracer to v5.41.1 by @duncanista in #637
• Use correct SecretsManager region by @nhulston in #639

Full Changelog: v10.122.0...v10.123.0

v10.122.0

Important

dd-trace-js version is v5.40.0

Warning

A regression was introduced in v5.39.0 of dd-trace-js which does not allow instrumentation for the fetch module properly, we recommend using layer v121 or downgrading the local tracer to 5.37.1.

What's Changed

• Performance improvement by lazy-loading a bunch of modules. See more details from the PRs by @rochdev in the list HERE
• DynamoDB payload tagging. dd-trace-js PR @joeyzhao2018
• Update Step Functions Parent ID Generation @avedmala
• Create bundle and publish to govcloud script @nhulston

arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:122
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:122
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:122

arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:122
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:122
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:122

Full Changelog: v10.121.0...v10.122.0

v10.121.0

Warning

This version contains a breaking change

What's Changed

• [gitlab] Get secrets from vault by @nhulston in #620
• Extract trace context from SNS->SQS event when SNS has raw message delivery by @nhulston in #621
• Deprecate Node.js 16.x by @nhulston in #624
• [Breaking change]: upgrade dd-trace to v5.37.1 by @nhulston in #625
• v10.121.0 by @nhulston in #626

arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:121
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:121
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:121

arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:121
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:121
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:121

Full Changelog: v9.120.0...v10.121.0

v9.120.0

What's Changed

• Use aws-sdk v3 for secrets manager by @DylanLovesCoffee in #616

Full Changelog: v9.119.0...v9.120.0

arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node16-x:120
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:120
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:120
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:120

arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node16-x:120
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:120
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:120
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:120

v9.119.0

What's Changed

• Redrive Trace Merging Fix by @avedmala in #605
• Extract API Key from Secrets Manager when using the metrics API client by @DylanLovesCoffee in #609
• Update DD_COLD_START_TRACING env var description by @nhulston in #611
• Move span pointer to inferred span; add env var to toggle span pointers by @nhulston in #607

Full Changelog: v9.118.0...v9.119.0

arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node16-x:119
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:119
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:119
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:119

arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node16-x:119
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:119
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:119
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:119

v9.118.0

What's Changed

• Add S3 Downstream Span Pointers by @nhulston in #587
• Redriven Step Functions Trace Merging by @avedmala in #598
• chore: upgrade dd-trace to v4.53.0 by @nhulston in #601
• Add DynamoDB Downstream Span Pointers by @nhulston in #600

Full Changelog: v9.117.0...v9.118.0

arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node16-x:118
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:118
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:118
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:118

arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node16-x:118
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:118
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:118
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:118

v9.117.0

What's Changed

• chore: upgrade dd-trace to v4.50.0 by @nhulston in #590
• chore: [SVLS-5989] add Node 22 support by @apiarian-datadog in #595

Full Changelog: v9.116.0...v9.117.0

arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node16-x:117
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:117
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:117
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:117

arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node16-x:117
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:117
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:117
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:117