Set tracing spans for rust client operations - #264
Merged
Conversation
richvdh
force-pushed
the
rav/rust_logging_spans
branch
from
August 5, 2026 22:02
5041b72 to
1adb3b5
Compare
richvdh
marked this pull request as ready for review
August 6, 2026 09:54
Closed
Closed
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
2 participants
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.
This means that most of the log lines from the Rust SDK are annotated with
CC[@user:id][device_id], which is helpful when there are multiple users/devices involved in a test.It's not perfect, mostly because the Rust SDK isn't perfect at propagating spans into background tasks that get forked, but it's a good start.