Releases: DataDog/datadog-lambda-python
v19
Layers
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python27:19
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python36:19
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:19
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:19
Changes
Get function_version
from function_arn
v18
Lambda Layer version 18
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python27:18
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python36:18
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:18
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:18
Changes
*. Add code change free handler
v17
Lambda Layer version 17
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python27:17
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python36:17
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:17
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:17
Replace <AWS_REGION> above with your Lambda's region and choose the layer ARN that specifies the runtime that your Lambda is using.
Changes:
- Fix for issue where root dd-trace span was being disguarded #60
v16
Lambda Layer version 16
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python27:16
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python36:16
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:16
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:16
Replace <AWS_REGION> above with your Lambda's region and choose the layer ARN that specifies the runtime that your Lambda is using.
Changes:
v15
DO NOT USE THIS VERSION!
A bug fix in on the way: #56
Lambda Layer version 15
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python27:15
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python36:15
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:15
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:15
Replace <AWS_REGION> above with your Lambda's region and choose the layer ARN that specifies the runtime that your Lambda is using.
Changes:
- Adds experimental dd-trace-py support, see README for details
v14
Lambda Layer version 14
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python27:14
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python36:14
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:14
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:14
Replace <AWS_REGION>
above with your Lambda's region and choose the layer ARN that specifies the runtime that your Lambda is using.
Changes:a
v13
Lambda Layer version 13
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python27:13
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python36:13
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:13
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:13
Replace <AWS_REGION>
above with your Lambda's region and choose the layer ARN that specifies the runtime that your Lambda is using.
Changes:
- Defaults the DD_LOGS_INJECTION option to true. This is a breaking change. Please test any custom Datadog pipelines you have handling Lambda logs after upgrade.
v12
Datadog Python Lambda Layer version 12
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python27:12
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python36:12
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:12
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:12
Replace <AWS_REGION>
above with your Lambda's region and choose the layer ARN that specifies the runtime that your Lambda is using.
Changes:
- Defaults the DD_ENHANCED_METRICS option to
true
- If DD_ENHANCED_METRICS is enabled, always writes enhanced metrics to stdout
- Breaking change: if you previously set the env var DD_ENHANCED_METRICS=true and did not set DD_FLUSH_TO_LOG=true, the enhanced metrics will no longer be submitted to Datadog synchronously; the metrics will now be written to logs. If you already have a Datadog Forwarder Lambda configured, that will read the enhanced metrics logs and submit the metrics asynchronously. If you do not have a Datadog Forwarder set up, you'll need to create one to get enhanced metrics into your Datadog account. See Datadog Forwarder Lambda setup instructions.
- Because of the breaking change above, we've bumped the major package version so that this release is version 1.12.0. We've set the minor version to 12 so that the minor version of our package stays in alignment with the version of the layer we're releasing.
v11
Lambda Layer version 11
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-PYTHON_RUNTIME:11
Replace PYTHON_RUNTIME
above with Datadog-Python27, Datadog-Python36, Datadog-Python37 or Datadog-Python38 to match your Lambda's Python runtime.
Changelog:
- Add python 3.8 support
- Upgrade dependencies
v10
Lambda Layer version 10
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-PYTHON_RUNTIME:11
Replace PYTHON_RUNTIME
above with Datadog-Python27, Datadog-Python36, Datadog-Python37 or Datadog-Python38 to match your Lambda's Python runtime.
Changelog:
- Support fetching API Key from secrets manager using
DD_API_KEY_SECRET_ARN
- Remove botocore to reduce package size
- Update dependencies