Repository navigation
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
DeliveryOptions.StartsNewLinkedTrace(and the same flag onEnvelope, so anIEnvelopeRulecan 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.
The flag travels as the
starts-new-linked-traceheader. Documented in the logging guide.🤖 Generated with Claude Code
https://claude.ai/code/session_01LtJfPt1KT4ZtrNDs2auuEV