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

[Question] What is correct way to call Context.current.span now? #173

Closed
dankhan-helmet opened this issue Jun 5, 2024 · 1 comment · Fixed by #176
Closed

[Question] What is correct way to call Context.current.span now? #173

dankhan-helmet opened this issue Jun 5, 2024 · 1 comment · Fixed by #176

Comments

@dankhan-helmet
Copy link

Prior to 0.18.1 I had used Context.current.span to access the current span and add attributes to it in my code.

This approach has been deprecated in recent versions, but the deprecation notes don't suggest or point to what to use instead.

I'm struggling to find documentation to tell me what the recommended way to do this is now. Any pointers? 🙏🏼

@dankhan-helmet
Copy link
Author

dankhan-helmet commented Jun 15, 2024

Note also this is the recommend way of calling it in the latest readme.md file, but that way is now deprecated.

"To avoid needing to pass spans around as arguments to other functions, you can get the current span with Context.current.span."

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 a pull request may close this issue.

1 participant