[FEATURE]: Best practice for temporarily pausing tracing

[marcelofern]

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

[wantsui]

Hi @marcelofern !

Can you clarify what you mean by stack trace?

My use case is that I use some external package that has a relatively big stack trace

Is it that there's span tag on the span that you don't want to see? Or is it that the duration of the span is skewed by the operations of this external package?

Without seeing the trace, I have to agree that this is a feature request. If you'd like to provide some more context to the use case, I recommend a support ticket so we can see what may be going on: https://docs.datadoghq.com/help/ .

Thanks!

[github-actions[bot]]

This issue has been automatically closed after a period of inactivity. If it's a feature request, it has been added to the maintainers' internal backlog and will be included in an upcoming round of feature prioritization. Please comment or reopen if you think this issue was closed in error.