Releases: DataDog/datadog-lambda-python
v74 (4.74.0)
What's Changed
- DD_SERVICE_MAPPING implementation for inferred spans by @zARODz11z in #333
- feat: add
peer.service
by @duncanista in #337 - fix: unit tests failing due change in internals of tracer by @duncanista in #340
- bump ddtrace to take advantage of new aws sdk request span tags & reg… by @zARODz11z in #341
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:74
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:74
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:74
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:74
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:74
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:74
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:74
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:74
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:74
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:74
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:74
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:74
Full Changelog: v73...v74
v73 (4.73.0)
What's Changed
- [downsizing] remove jsonshema/tests dir by @joeyzhao2018 in #327
- enforce urllib3 version by @joeyzhao2018 in #335
- set_correlation_ids should handle the empty context case by @joeyzhao2018 in #334
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:73
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:73
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:73
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:73
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:73
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:73
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:73
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:73
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:73
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:73
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:73
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:73
Full Changelog: v72...v73
v72 (4.72.0)
What's Changed
- Using ddtrace==1.12.1
- #323 Env variables depend on DD_TRACE_ENABLED , i.e. false if DD_TRACE_ENABLED false
- DD_COLD_START_TRACING for cold start aws.lambda.import spans
- DD_TRACE_MANAGED_SERVICES for inferred spans
- DD_DECODE_AUTHORIZER_CONTEXT and DD_ENCODE_AUTHORIZER_CONTEXT for lambda authorizor spans (a special case for inferred spans)
- #325 Authorizer lambda python3.7 bug fix
- #322 Make the layer size smaller
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:72
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:72
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:72
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:72
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:72
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:72
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:72
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python37:72
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:72
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:72
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:72
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:72
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:72
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:72
Full changelog: v71...v72
v71
What's Changed
- Add Python 3.10 support
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:71
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:71
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:71
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:71
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:71
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:71
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:71
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python37:71
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:71
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:71
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:71
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:71
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:71
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:71
Full changelog: v70...v71
v70
What's Changed
- Lambda and Step Functions Span Linking #320
- Modify end time of lambda load span to be last cold start node's end_time #319
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:70
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:70
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:70
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:70
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:70
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python37:70
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:70
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:70
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:70
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:70
Full changelog: v69...v70
v69
The impact is limited to Lambda functions with the environment variable DD_MERGE_XRAY_TRACES
set to true
. You can use the following metric query to find impacted Lambda functions in your Datadog orgs.
sum:aws.lambda.invocations{runtime:python*,dd.merge_xray_traces:true} by {aws_account,region,functionname}.as_count()
The impacted Lambda functions will
- produce incomplete traces without the aws.lambda span if you have tracing enabled
- produce the following errors to the logs
Traceback (most recent call last): File "/var/task/datadog_lambda/wrapper.py", line 247, in _before set_dd_trace_py_root(trace_context_source, self.merge_xray_traces) File "/var/task/datadog_lambda/tracing.py", line 542, in set_dd_trace_py_root context = dict(dd_trace_context) TypeError: 'NoneType' object is not iterable
However,
- The errors do NOT crash or degrade your application
- There are no impact to metrics and logs collection
- There are no impact to APM traces except for the aws.lambda spans
Although the error is non-fatal, we still recommend upgrade your datadog-lambda-library to the current version.
- if you installed the datadog-lambda-python into your deployment package using pip, then you need to update the version to 4.69.0 in requirements.txt and redeploy.
- if you installed the Datadog Lambda layer for Python, such as Datadog-Python38:68, you need to update the layer version to 69, in your CDK construct or SAM transform.
- If you are using the plugin for serverless framework, you need to upgrade to v5.21.0.
What's Changed
- use ddsaml2aws by @joeyzhao2018 in #301
- redact dd-api-key by @joeyzhao2018 in #307
- feat: support LINEAGE field on x-ray trace ID by @astuyve in #310
- fix the flaky test_exec_module_failure_case by enforcing the _cold_st… by @joeyzhao2018 in #311
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:69
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:69
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:69
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:69
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:69
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python37:69
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:69
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:69
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:69
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:69
Full Changelog: v68...v69
v68
What's Changed
- cold start tracing (python) by @joeyzhao2018 in #299
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:68
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:68
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:68
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:68
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:68
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python37:68
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:68
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:68
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:68
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:68
Full Changelog: v4.67.0...v68
v67
What's Changed
- issue 295 by @joeyzhao2018 in #296
- build: relax
datadog
version by @filip-halemba in #290
New Contributors
- @filip-halemba made their first contribution in #290
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:67
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:67
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:67
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:67
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:67
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python37:67
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:67
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:67
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:67
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:67
Full Changelog: v66...v67
v66
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:66
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:66
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:66
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:66
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:66
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python37:66
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:66
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:66
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:66
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:66
Full Changelog: v65...v66
v65
- Authorizer trace context (#256)
- Use context.aws_request_id instead of http payload's requestId in the spans' tags (#266)
- Handle custom detail field in Lambda event payloads (#276)
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python37:65
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38:65
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:65
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:65
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:65
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python37:65
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:65
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:65
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:65
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:65
Full Changelog: v64...v65