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

[FEATURE]: Best practice for temporarily pausing tracing #12462

Open
marcelofern opened this issue Feb 20, 2025 · 0 comments
Open

[FEATURE]: Best practice for temporarily pausing tracing #12462

marcelofern opened this issue Feb 20, 2025 · 0 comments

Comments

@marcelofern
Copy link

marcelofern commented Feb 20, 2025

Package Name

N/A

Package Version(s)

N/A

Describe the goal of the feature

I can't find in the documentation information on how to "pause" the current
tracer.

My use case is that I use some external package that has a relatively big stack
trace that I don't care about, and would thus prefer to omit it because it adds
too much data.

Describe the goal of the feature

It would be great to add in the documentation information on how to perform the
above.

By reading the docs I came across:

  • tracer.shutdown()
  • followed by tracer.configure(enabled=True)

as a possible alternative. But I am alarmed by calling tracer.shutdown().

More clarification on this through docs would be deeply appreciated.
Thanks!

Is your feature request related to a problem?

No, it's related to documentation enhancements.

Describe alternatives you've considered

tracer.shutdown and tracer.configure

Additional context

N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant