Skip to content

[SVLS-8704] Set durable_function.execution_status on END platform logs#1188

Open
lym953 wants to merge 4 commits intomainfrom
yiming.luo/durable-status-tag
Open

[SVLS-8704] Set durable_function.execution_status on END platform logs#1188
lym953 wants to merge 4 commits intomainfrom
yiming.luo/durable-status-tag

Conversation

@lym953
Copy link
Copy Markdown
Contributor

@lym953 lym953 commented Apr 16, 2026

Summary

  • Sets durable_function.execution_status as a log attribute on END platform logs (END RequestId:) for durable function invocations
  • The value is read from aws_lambda.durable_function.execution_status tag of the aws.lambda span, added by the tracer

Automated testing

  • Added test_execution_status_on_end_log covering both the status-present (SUCCEEDED) and status-absent (None) cases

Manual testing

For durable functions, execution status is added to END log:
image

@lym953 lym953 changed the title [SVLS-8583] Set durable_function.execution_status on END platform logs [SVLS-8704] Set durable_function.execution_status on END platform logs Apr 16, 2026
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@lym953 lym953 force-pushed the yiming.luo/durable-status-tag branch from ca78ba9 to 53a9b6b Compare April 16, 2026 16:02
lym953 and others added 2 commits April 16, 2026 12:28
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@lym953 lym953 marked this pull request as ready for review April 16, 2026 16:31
@lym953 lym953 requested a review from a team as a code owner April 16, 2026 16:31
@lym953 lym953 requested review from Copilot and shreyamalpani and removed request for Copilot April 16, 2026 16:31
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR propagates Durable Function execution status from tracer span tags into Lambda END platform logs so the log stream can be correlated with final durable execution outcomes.

Changes:

  • Extract aws_lambda.durable_function.execution_status from the aws.lambda span and forward it through the invocation/logs pipeline.
  • Add a new log attribute durable_function.execution_status (serialized under message.lambda) and set it on END logs.
  • Add a unit test covering status-present and status-absent cases for END logs.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
bottlecap/src/traces/trace_agent.rs Extracts execution status from span metadata and forwards it with the durable context.
bottlecap/src/tags/lambda/tags.rs Adds the durable execution status span tag constant.
bottlecap/src/logs/processor.rs Threads execution status through the durable context update handling.
bottlecap/src/logs/lambda/processor.rs Stores execution status in durable context and applies it to END logs; adds a test.
bottlecap/src/logs/lambda/mod.rs Adds durable_function.execution_status to the serialized Lambda log schema.
bottlecap/src/lifecycle/invocation/processor_service.rs Extends the durable context forwarding command to include execution status.
bottlecap/src/lifecycle/invocation/processor.rs Forwards execution status to the logs agent via DurableContextUpdate.

Comment thread bottlecap/src/traces/trace_agent.rs Outdated
Comment thread bottlecap/src/logs/lambda/processor.rs
Comment thread bottlecap/src/logs/lambda/processor.rs
…a clone

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants