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

Spike - investigate how to enable/disable tracing on a per-module basis #31

Open
Notgnoshi opened this issue Nov 19, 2023 · 0 comments
Open
Labels
documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested

Comments

@Notgnoshi
Copy link
Member

Motivated by #12 (comment)

Having optional tracing is great, but as the project grows, adding tracing around everything will get quite verbose. We should find a way to let a developer enable tracing only for the modules they want.

We'd probably want to use https://docs.rs/tracing-subscriber/0.3.18/tracing_subscriber/#layers-and-filters for this?

Would this be defined entirely in user code? Or are there hooks we have to provide in the library itself? Regardless, we'll want to provide documentation to show users/developers how to adjust things.

@Notgnoshi Notgnoshi added documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested labels Nov 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant