Skip to content
New issue

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

Allow settings tags directly on transactions/spans #699

Merged
merged 1 commit into from
Oct 24, 2024

Conversation

nrxus
Copy link
Contributor

@nrxus nrxus commented Oct 18, 2024

currently the only tags added to transactions are the tags on the scope at the time you finish a transaction. Sometimes, however, it is useful to have tags that aren't for the scope but just for the transaction.

I am using the same signature as the equivalent method in Scope.

I know there are currently other PRs related to tags in transactions but I think those are more specific to the tracing integration so having methods to do it explicitly in a transaction (or span) is still useful.

currently the only tags added to transactions are on the scope at the
time of finish, but sometimes it is useful to have tags that aren't
for the scope but just for the transaction
@nrxus
Copy link
Contributor Author

nrxus commented Oct 24, 2024

@Swatinem, thanks for the approval. Is there anything I need to do before it gets merged?

@Swatinem Swatinem merged commit a1481d4 into getsentry:master Oct 24, 2024
14 checks passed
@Swatinem
Copy link
Member

Ah yes, this slipped my radar, as I don’t think anyone at the moment really maintains this repo/SDK actively.

@nrxus
Copy link
Contributor Author

nrxus commented Oct 24, 2024

Thanks for the merge! If you are all okay with someone that doesn't work at sentry to help maintain (by reviewing/approving PRs) let me know. My team actively uses this crate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants