-
Notifications
You must be signed in to change notification settings - Fork 500
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
(3) Move tracing related functions from Hub to Scope #2558
(3) Move tracing related functions from Hub to Scope #2558
Conversation
…y-python into antonpirker/refactor-hub
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. This stuff also fits better on the scope conceptually.
…scopes the hub is removed and the root level API directly calls it on the scope
Co-authored-by: Ivana Kellyerova <ivana.kellyerova@sentry.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this one is good because this stuff conceptually now belongs together with propagation context 👍
Moved some functionality from Hub to Client: - moved `start_transaction` from Hub to Scope - moved `start_span` from Hub to Scope - moved `continue_trace` from Hub to Scope This is preparation work for refactoring how we deal with Hubs and Scopes in the future. Depends on: #2558 (please review the linked one first)
Moved some functionality from Hub to Client:
get_traceparent
from Hub to Scopeget_baggage
from Hub to Scopeiter_trace_propagation_headers
from Hub to Scopetrace_propagation_meta
from Hub to ScopeThis is preparation work for refactoring how we deal with Hubs and Scopes in the future.
Depends on: #2555 (please review the linked one first)