Warning
⚠️ This release contains some breaking changes ⚠️
🛠️ Fixes and enhancements
- @zarirhamza AWS Service Naming Overhaul (#655, #666)
⚠️ Service names are now reflect the actual AWS resource name instead of being vague. The old to new mappings are:aws.lambda
→[function_name]
aws.dynamodb
→[table_name]
aws.sns
→[topic_name]
aws.sqs
→[queue_name]
aws.kinesis
→[stream_name]
aws.s3
→[bucket_name]
aws.eventbridge
→[event_name]
- To opt out and restore old behavior, use the env var:
DD_TRACE_AWS_SERVICE_REPRESENTATION_ENABLED=false
- Dashboards, monitors, or alerts using
service
as a filter may break.- Recommended fix: Switch to using
operation_name
with same value to achieve old behavior.
- Recommended fix: Switch to using
- Sampling rules may need to be updated to reflect the new service names
Other Changes
DD_SERVICE
now takes precedence when setting the service name on Lambda spans.- AWS spans are now correctly marked with
span.kind: server
. - Removed outdated service override logic
- Cold start tracing config now uses a boolean (
true
/false
) instead of numeric (1
/0
).
Important
This version imports dd-trace-js
v5.58.0
# AWS Commercial
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node18-x:127
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node20-x:127
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Node22-x:127
# AWS GovCloud
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node18-x:127
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node20-x:127
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Node22-x:127
Full Changelog: v11.126.0...v12.127.0