We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is related to what was solved in this PR: #629
Currently all spans are propagated to context. I feel what's missing is that spans named "tags" should instead be propagated to tags in Sentry.
At a glance it should be sufficient to add a check in the arms of this match
sentry-rust/sentry-tracing/src/converters.rs
Lines 71 to 88 in acba14f
tags
tags.{}
{}.{}
The text was updated successfully, but these errors were encountered:
TBH, this feels a bit too magical, and might lead to some surprises as well.
Especially if you happen to have such a function:
#[tracing::instrument] fn tags(arg: ()) { }
This is an interesting idea though, and may be something to put more thought into.
Sorry, something went wrong.
No branches or pull requests
This is related to what was solved in this PR: #629
Currently all spans are propagated to context. I feel what's missing is that spans named "tags" should instead be propagated to tags in Sentry.
At a glance it should be sufficient to add a check in the arms of this match
sentry-rust/sentry-tracing/src/converters.rs
Lines 71 to 88 in acba14f
tags
, then the key should be formatted astags.{}
, rather than the current{}.{}
.The text was updated successfully, but these errors were encountered: