fix(tracing): mirror message id on spans - #136
Merged
Merged
Conversation
This was referenced Jun 3, 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
1 participant
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.
Summary
agyn.thread.message.idonto each exported span attribute as well as the resource attribute.Refs #135
Tracks agynio/agents-orchestrator#207.
Validation
git diff --checkgo test ./internal/tracingproxy ./internal/daemongo test ./...go vet ./...Latest agents-orchestrator E2E after init-image pins still fails only on claude/codex
ListSpans(filter: { messageId })while go-core expose lifecycle passes; this PR is the next owning daemon-side fix.