AWS Lambda Durable Functions observability with OpenTelemetry
Compute Blog
This article explains how to use the OpenTelemetry plugin for AWS Durable Execution SDK to gain end-to-end observability of Lambda durable functions that span multiple invocations.
- Durable functions fragment traces across invocations; the OTel plugin generates deterministic trace IDs to unify them
- Install the plugin, add the ADOT Lambda layer, enable X-Ray active tracing, and configure the plugin in your handler
- Each step, wait, and callback operation gets its own span with accurate wall-clock timing and continuation links
- Logs are automatically enriched with traceId and spanId for correlation across all invocations
- Cold start overhead is 40–60 MB; use Lambda Power Tuning to measure impact for your workload
- Configure sampling to control Amazon CloudWatch Application Signals costs at high volumes
- The plugin supports execution view for short workflows and invocation view for long-running executions
The OpenTelemetry plugin enables operators to see complete timelines from start to finish, including zero-cost waits, while maintaining vendor flexibility through open standards.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Oct 28
2026
2026
Observing AWS Lambda durable functions with the Durable Execution Telemetry Exporter
Oct 28
2026
2026
AWS Lambda durable functions now exports live telemetry for execution insights
Aug 14
2026
2026
Observability best practices for Lambda durable functions
Sep 12
2024
2024
Enhancing Observability in the AWS SDK for .NET with OpenTelemetry
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.