-
-
Notifications
You must be signed in to change notification settings - Fork 164
Add option to enable propagation of parent span tags #746
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
base: master
Are you sure you want to change the base?
Conversation
665dca2
to
efbc35b
Compare
Hi @DoumanAsh , thanks for the PR and sorry for the wait here! |
Would test case suffice or what sort of example you'd like to see? |
Actually I kinda forgot about it, but looking back at implementation, event stores fields in context I also see that iterator over data does not include tags... so this PR is incorrect |
No problem. I don't clearly see how, but maybe this might be affected by 3bcdda3 |
@lcian Actually I know what is problem is and it is very trivial mistake on my part |
Nice, thanks! |
7344609
to
9c0df4f
Compare
@lcian I refactored my code to correctly look up span's tags on new event (this of course not possible for breadcrumbs, but events/exceptions should be working as it carries tags) |
I think this makes sense, thanks. |
It is kinda not really used without context so I made it together |
985d0ed
to
0e59852
Compare
Rebased and refactored context passing |
0e59852
to
534df04
Compare
Thank you, will take a look soon! |
534df04
to
de85f12
Compare
I would like to suggest option to allow event's spans to automatically insert first available tag as tag within event, rather than propagating it as additional data
Old behavior can be used together with this feature too
But I often find it inconvenient that events may not contain tags from within span (especially if spans get rate limited at sentry)
What do you think about this addition?
Let me know if you'd like me to make some adjustments to PR