Important
dd-trace-py version is v3.7.0
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python38-ARM:109
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39:109
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python39-ARM:109
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310:109
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python310-ARM:109
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311:109
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python311-ARM:109
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python312:109
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python312-ARM:109
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python313:109
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Python313-ARM:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python38-ARM:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python39-ARM:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python310-ARM:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python311-ARM:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python312:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python312-ARM:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python313:109
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Python313-ARM:109
What's Changed
- fix: timestamps we send to the extension should be integers by @apiarian-datadog in #590
Full Changelog: v6.108.0...v6.109.0
Contributors
apiarian-datadog