If you don't see datadog-lambda-java in your application's pom.xml or build.gradle file, you can stop reading. Otherwise, you need to upgrade its version to 1.4.10 (the current version) and redeploy.
If you are not sure, you can use the following metric query in Datadog to find out impacted Lambda functions.
sum:aws.lambda.enhanced.invocations{runtime:java*,datadog_lambda:*} by {aws_account,region,functionname}.as_count()
This library was deprecated and it was used to trace your Lambda function and send the traces over CloudWatch logs with the help of the Datadog Forwarder Lambda functions. However, we recently identified that this library was incompatible with the newly added Lineage field to the X-Ray tracing header. This change has already been observed in eu-west-1 and eu-north-1 regions, and AWS will gradually roll out the change to the remaining regions in the next few weeks.
The impacted Lambda functions will
- produce incomplete traces without the aws.lambda span if you have tracing enabled
- produce
Malformed _X_AMZN_TRACE_ID valueerrors to the logs
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
dd-trace-java version (tracer tag) v1.5.0
dd-trace-java layer ARN:
arn:aws:lambda:<AWS_REGION>:464622532012:layer:dd-trace-java:8