v8.113.0

Warning

⚠️ This release contains some breaking changes ⚠️

🛠️ Fixes and enhancements

• @zarirhamza AWS Service Naming Overhaul (#635)
  • ⚠️ 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.

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

Important

dd-trace-py version is v3.11.0

Tip

The lambda layers' zip files are provided here

arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:113
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:113
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:113
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:113
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:113
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:113
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:113
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python312:113
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python312-ARM:113
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python313:113
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python313-ARM:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python312:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python312-ARM:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python313:113
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python313-ARM:113

Full Changelog:

• datadog-lambda-python v7.112.0...v8.113.0

• ddtrace DataDog/dd-trace-py@v3.10.2...v3.11.0