v1.11.0

This release add support for trace context propagation through SQS. When the lambda function is a consumer of messages from an SQS queue, the tracer will now properly extract trace context from the messages and apply them. This will result in connected traces between the producer and consumer. (#142)

v1.10.0

• Bump dd-trace-go to v1.54.1

v1.9.0

• Retry sending trace payloads on failure #128

v1.8.0

• Upgrade AWS SDK Go to v2 #113
• Add support for universal instrumentation with the extension #116
• Include error in failed metric send log #118

v1.7.0

Bump dd-trace-go to v1.41.0

v1.6.0

Bump dd-trace-go to latest version to address some vulnerabilities.

What's Changed

• Bump dd-trace-go to latest version to address some vulnerabilities by @kimi-p in #109

New Contributors

• @kimi-p made their first contribution in #109

Full Changelog: v1.5.0...v1.6.0

v1.5.0

• Updates fasthttp dependency #107

v1.4.0

Do not show error messages even if neither DD_API_KEY nor DD_KMS_API_KEY is set when Lambda Extension is running #102

v1.3.0

Add functionname attribute to span metadata (#89)

v1.2.0

Features

• Support custom root trace extraction from Lambda body content (#80)

Allows the user to create define a custom TraceContextExtractor to extract the datadog trace context from non-API-Gateway Lambda events.

Bug fixes

• Set default sampling priority to sampler-keep (#88)

If datadog-lambda-go gets a datadog trace context that does not have a sampling-priority set, it will default to sampler-keep (old behavior was to discard the entire trace context as malformed).