Repository navigation
GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids - #5117
Merged
Merged
Conversation
…ion and trace ids MessageActivityReport gains trailing columns on every row: message id, correlation id, causation id, saga id, trace id and activity id, so a reader (a coding agent above all) can join a row to the application's OpenTelemetry traces and logs. Causation is the envelope's ConversationId, which Wolverine sets to the id of the message that caused it; it is blank for a message that starts a chain. Envelope.ParentId is the OTel parent activity, not the causing message, so it is not used for causation. HttpExchangeReport gains a correlation id column with the X-Correlation-ID the act sent, which lines an HTTP act up with the messages it caused. The old Add overload is kept and delegates. Closes #5106 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DCggXgxnG3EBXoR9rrq37U
This was referenced Oct 23, 2026
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.
Closes #5106.
What
MessageActivityReportgains trailing columns on every row (option 1 from the issue):message id,correlation id,causation id,saga id,trace id,activity id.HttpExchangeReportgains acorrelation idcolumn holding theX-Correlation-IDthe act sent. That is the correlation id of every message the endpoint caused, so the two reports line up. The oldAddoverload is kept and delegates to the new one, so the public API doesn't break.One correction to the issue's mapping
Envelope.ParentIdis the OpenTelemetry parent activity id, not the message that caused this one. The causing message's id isEnvelope.ConversationId:MessageContextsets it to the incoming envelope'sId, andMessageBussets it to the message's own id for a message that starts a chain. Socausation idisConversationId, and it is blank when that equals the envelope's own id. The trace id isEnvelopeRecord.RootId(the W3C trace id), and the activity id isEnvelopeRecord.ActivityId.Tests
cascaded_messages.the_message_activity_carries_the_ids_that_join_it_to_the_telemetry: the act's row has the act's correlation id and no causation, and each cascadedSendConfirmationEmailrow has the same correlation id with the act's message id as its causation.posting_commands.the_exchange_rides_along_as_a_reportasserts the correlation id cell.dotnet build wolverine.slnx -c Release -f net9.0is clean.The docs paragraph in
docs/guide/testing-with-bobcat.mdgot a short factual addition and is worth a pass in your own voice.🤖 Generated with Claude Code
https://claude.ai/code/session_01DCggXgxnG3EBXoR9rrq37U