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

log level of metadata blob should be trace #623

Closed
brenzi opened this issue Jul 20, 2023 · 0 comments · Fixed by #674
Closed

log level of metadata blob should be trace #623

brenzi opened this issue Jul 20, 2023 · 0 comments · Fixed by #674
Labels
F7-enhancement Enhances an already existing functionality Q0-trivial

Comments

@brenzi
Copy link
Contributor

brenzi commented Jul 20, 2023

with RUST_LOG=info I get a ton of data which isn't helpful in 99% of all cases

[2023-07-20T15:03:15Z INFO  substrate_api_client::rpc::ws_client] sending request: {"id":"1","jsonrpc":"2.0","method":"state_getMetadata","params":[null]}
[2023-07-20T15:03:15Z INFO  substrate_api_client::rpc::ws_client] Got get_request_msg {"jsonrpc":"2.0","result":"0x6d6574610eb103000c1c73705f...   KILOBYTES .... .84ad03","id":"1"}

as these log messages are generic, and in general very helpful to be in info level (or maybe debug)
It may make sense to send the log to trace if the message is bigger than a certain size and only report a digest on info level

@brenzi brenzi changed the title log level of metadata should be trace log level of metadata blob should be trace Jul 20, 2023
@haerdib haerdib added F7-enhancement Enhances an already existing functionality Q0-trivial labels Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F7-enhancement Enhances an already existing functionality Q0-trivial
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants