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

Send span origin #668

Closed
Tracked by #14
stephanie-anderson opened this issue Jul 12, 2023 · 1 comment · Fixed by #849
Closed
Tracked by #14

Send span origin #668

stephanie-anderson opened this issue Jul 12, 2023 · 1 comment · Fixed by #849

Comments

@stephanie-anderson
Copy link

stephanie-anderson commented Jul 12, 2023

Trace origin indicates what created a trace or a span. Not all traces and spans contain enough information to tell whether the user or what precisely in the SDK created it. Origin solves this problem. Origin can be sent with the trace context or spans. The SDKs must set this value automatically. Users are not expected to set it manually. For more information, visit the develop docs.

As the origin for trace context and spans is optional, every SDK can decide whether to start sending the origin for everything or just selected transactions and spans. This issue is important for internal data analysis to understand the quality of our traces.

@natikgadzhi
Copy link
Contributor

@greywolve @cleptric cool if I work on this? I'm about to work on the Ruby equivalent of this, so I'm more or less in that context anyway.

@ribice ribice mentioned this issue Jul 1, 2024
@stephanie-anderson stephanie-anderson changed the title Send trace origin Send span origin Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants