Releases: DataDog/datadog-lambda-python
v87
Packaged dd-trace-py version 2.3.3
What's Changed
- Do not call flush extension after each invocation. (#406)
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:87
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:87
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:87
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:87
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:87
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:87
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:87
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:87
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python312:87
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python312-ARM:87
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:87
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:87
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:87
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:87
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:87
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:87
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:87
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:87
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python312:87
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python312-ARM:87
Full Changelog: v86...v87
v86
What's Changed
- Support Python 3.12 by @purple4reina in #392
- feat: Drop py3.7 by @astuyve in #395
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:86
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:86
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:86
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:86
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:86
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:86
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:86
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:86
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python312:86
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python312-ARM:86
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:86
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:86
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:86
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:86
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:86
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:86
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:86
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:86
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python312:86
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python312-ARM:86
Full Changelog: v85...v86
v85
Packaged dd-trace-py
What's Changed
Note this version fixes two bugs found in both v83 and v84.
- Use xray context span id when it exists, by @danielebra (#401)
- Ensure dummy metadata segment is json serializable, by @purple4reina thanks to @danielebra (#403)
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:85
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:85
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:85
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:85
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:85
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:85
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:85
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:85
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:85
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:85
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:85
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:85
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:85
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:85
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:85
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:85
Full Changelog: v84...v85
v84
Bug: TypeError: Object of type Context is not JSON serializable
There is a known bug in this version of the datadog_lambda library and it's related Lambda layer versions. It is recommended at this time to roll back to v82 until a fix can be released. Effected users will see the error TypeError: Object of type Context is not JSON serializable occur before their lambda function code executes. See #402 for more details.
Packaged dd-trace-py
Full layers:
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:84
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:84
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:84
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:84
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:84
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:84
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:84
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:84
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:84
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:84
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:84
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:84
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:84
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:84
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:84
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:84
Full Changelog: v83...v84
v83
Bug: TypeError: Object of type Context is not JSON serializable
There is a known bug in this version of the datadog_lambda library and it's related Lambda layer versions. It is recommended at this time to roll back to v82 until a fix can be released. Effected users will see the error TypeError: Object of type Context is not JSON serializable occur before their lambda function code executes. See #402 for more details.
Breaking change
This is a new major version, which is only breaking as we are upgrading dd-trace-py to v2.x, which is the latest supported release.
We do not expect major disruption for Lambda users, but the full list of changes is available here
As always we recommend all users test this major change in dev/staging environments before deploying to production environments.
Full layers:
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:83
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:83
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:83
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:83
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:83
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:83
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:83
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:83
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:83
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:83
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:83
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:83
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:83
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:83
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:83
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:83
What's Changed
- Defer trace context extraction to ddtrace. by @purple4reina in #391
- feat: push layers in batches by @astuyve in #393
- feat(breaking): ddtrace 2.3 by @astuyve in #394
- Improve error log message when no sns->sqs context found. by @purple4reina in #396
Full Changelog: v82...v83
v82
Packaged dd-trace-py
What's Changed
- feat: opt-in enablement of the instrumentation telemetry client #386
- feat: new env added
DD_CAPTURE_LAMBDA_PAYLOAD_MAX_DEPTH#387 #390 - misc: new section in the README.md file for env variables information
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:82
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:82
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:82
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:82
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:82
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:82
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:82
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:82
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:82
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:82
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:82
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:82
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:82
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:82
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:82
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:82
Full Changelog: v81...v82
v81
What's Changed
- feat: Pin dd trace below 2 by @astuyve in #374
- feat: Support urllib3 <= 2.1 for py 3.11 by @astuyve in #380
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:81
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:81
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:81
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:81
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:81
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:81
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:81
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:81
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:81
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:81
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:81
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:81
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:81
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:81
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:81
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:81
Full Changelog: v80...v81
v80
What's Changed
- When
DD_CAPTURE_LAMBDA_PAYLOADenabled, the values in lambda requests/responses will be tagged to the span as strings even for number or boolean values. - Support
chalice.app.Responseand also any custom response/request classes if the classes have either__str__orto_dict()implemented.
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:80
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:80
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:80
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:80
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:80
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:80
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:80
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:80
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:80
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:80
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:80
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:80
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:80
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:80
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:80
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:80
Full Changelog: v79...v80
v79 (datadog-lambda 4.79.0)
What's Changed
- feat: Support DD_TRACE_OTEL_ENABLED env var #361
- misc: change the traceback format to print in one line #362
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:79
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:79
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:79
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:79
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:79
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:79
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:79
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:79
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:79
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:79
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:79
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:79
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:79
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:79
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:79
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:79
Full Changelog: v78...v79
v78
What's Changed
- feat: EventBridge to SQS support by @duncanista in #358
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:78
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:78
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:78
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:78
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:78
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:78
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:78
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:78
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:78
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:78
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:78
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:78
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:78
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:78
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:78
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:78
Full Changelog: v77...v78