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

Runtime configuration of tracing directives #564

Open
ten3roberts opened this issue Jul 6, 2023 · 2 comments
Open

Runtime configuration of tracing directives #564

ten3roberts opened this issue Jul 6, 2023 · 2 comments
Labels
enhancement New feature or request topic:web Related to running on the Web

Comments

@ten3roberts
Copy link
Contributor

Tracing event filtering can currently be filtered using RUST_LOG env, which is combined with our defaults (a gotcha we've stumbled on many times as you think you enabled the logs you wanted but they got silenced yet).

This is not possible for the web client as there is no concept of env. All logs >= debug are currently emitted.

It would be great to have a console or settings panel, possibly in the debugger, where you can type in a filtering directive at runtime. This would allow you to filter or enable verbose logs for only certain crates or modules, which is incredibly useful for debugging.

Eliza has a similar demonstration of runtime directives that we would want to achieve: https://youtu.be/JjItsfqFIdo?t=498

@ten3roberts ten3roberts added enhancement New feature or request topic:web Related to running on the Web labels Jul 6, 2023
@ten3roberts
Copy link
Contributor Author

#151

@philpax
Copy link
Contributor

philpax commented Jul 31, 2023

See also #219

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request topic:web Related to running on the Web
Projects
None yet
Development

No branches or pull requests

2 participants