Skip to content

Let an outgoing message start a new trace linked to its sender - #1

Open
jakobt wants to merge 1 commit into
mainfrom
jta/new-linked-trace-per-message
Open

jakobt wants to merge 1 commit into
mainfrom
jta/new-linked-trace-per-message

Conversation

@jakobt

@jakobt jakobt commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Adds DeliveryOptions.StartsNewLinkedTrace (and the same flag on Envelope, so an IEnvelopeRule can set it). A marked message starts a new trace on the receiving side: its first span is a root with a span link to the sending activity, and later spans for the message, retries included, join that new trace. The correlation id is unchanged.

When a handler fans out into many messages, every message they cause lands in one trace that grows without bound. The OpenTelemetry messaging conventions correlate a producer with such consumers through span links rather than parenting, which is also how Wolverine already links a retry to the failed attempt before it.

await bus.SendAsync(new ProcessItem(id), new DeliveryOptions { StartsNewLinkedTrace = true });

The flag travels as the starts-new-linked-trace header. Documented in the logging guide.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LtJfPt1KT4ZtrNDs2auuEV

DeliveryOptions.StartsNewLinkedTrace and Envelope.StartsNewLinkedTrace mark
a message so the first span Wolverine starts for it on the receiving side is
the root of a new trace with a span link to the sending activity, as the
OpenTelemetry messaging conventions do for fan-out. Later spans for the same
message, retries included, join the new trace. The flag travels as the
starts-new-linked-trace header.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LtJfPt1KT4ZtrNDs2auuEV
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.

1 participant