Releases: DataDog/datadog-lambda-extension
Releases · DataDog/datadog-lambda-extension
v38
Agent tag
Agent Version: 7.42.1
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension:38
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension-ARM:38
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension:38
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension-ARM:38
What's Changed
- Honor DD_ENHANCED_METRICS env variable.
- add masks for numbers to prevent output by @maxday in #116
- Add performance optimization for Java by @DarcyRaynerDD in #117
v37
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension:37
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension-ARM:37
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension:37
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension-ARM:37
What's Changed
- Do not try to enable log api for local testing: DataDog/datadog-agent#15229
- Remove old code that caused a crash when trying to retrieve secrets manager keys: DataDog/datadog-agent#15551
- Respect DD_PROXY_HTTP/DD_PROXY_HTTPS for secrets manager and KMS clients: DataDog/datadog-agent#15574
v36
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension:36
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension-ARM:36
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension:36
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension-ARM:36
What's Changed
- Fix when we don't get spans from Telemetry API: DataDog/datadog-agent#14396
- Buffer cold start traces to handle out of order delivery of metric and span: DataDog/datadog-agent#14664
- Fix startup log buffering and log/trace correlation: DataDog/datadog-agent#14207
v35
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension:35
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension-ARM:35
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension:35
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension-ARM:35
What's Changed
v34
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension:34
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension-ARM:34
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension:34
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension-ARM:34
What's Changed
- Uses the v1 metrics API for Serverless
v33
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension:33
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension-ARM:33
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension:33
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension-ARM:33
What's Changed
- When a function cold starts, a span is now created representing the time and duration of function initialization
- Adds three new metrics:
aws.lambda.enhanced.response_latency
,aws.lambda.enhanced.response_duration
, andaws.lambda.enhanced.produced_bytes
v32
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension:32
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension-ARM:32
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension:32
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension-ARM:32
What's Changed
- Fix CVE-2022-27664
v31
There is a conflict with V30 during publishing the new extension, so V31 is the new version after V29.
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension:31
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension-ARM:31
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension:31
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension-ARM:31
What's Changed
-
Append to JAVA_TOOL_OPTIONS instead of override by @astuyve in #86
-
Small readability updates and other nitpicks by @purple4reina in DataDog/datadog-agent#13856
-
Load proxy config from datadog.yaml for metric agent and solve the problem of wrong request ID log by @nine5two7 in DataDog/datadog-agent#13790
v29
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension:29
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension-ARM:29
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension:29
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension-ARM:29
v28
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension:28
arn:aws:lambda:<AWS_REGION>:464622532012:layer:Datadog-Extension-ARM:28
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension:28
arn:aws-us-gov:lambda:us-gov-<AWS_REGION>:002406178527:layer:Datadog-Extension-ARM:28