Skip to content

log level of metadata blob should be trace #623

@brenzi

Description

@brenzi

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions