-
Notifications
You must be signed in to change notification settings - Fork 35
chore: use get_tracer() for all tracer access #822
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: main
Are you sure you want to change the base?
Conversation
2b5870f to
408d425
Compare
pvital
left a comment
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.
Just "a few" changes!
@CagriYonca, please, in addition to the change requests, fix this failed condition. |
Signed-off-by: Cagri Yonca <[email protected]>
Signed-off-by: Cagri Yonca <[email protected]>
408d425 to
9598863
Compare
…nd with_blinker) instrumentations Signed-off-by: Cagri Yonca <[email protected]>
a9cba61 to
2ffdf6b
Compare
|



We should use the get_tracer function to provide the correct use case of the singleton pattern, so we can start by adapting our code to getter and setters. Using singletons with getters and setters may also be helpful in resolving span_queue access management issues that arise from multi-threading with Instana.