You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a lot of different trace targets, and we don't have any broad overview of what trace targets someone might want to turn on if they're trying to debug a component or protocol.
We should list all specific log targets, for example some crates have log targets that are different than the crate name or are organized differently than just with crates:
The docs should try to explain whether or not the log level makes a difference, and what gets logged, for example:
reth_eth_wire has trace! and debug! targets. It outputs RLPx session related information with trace targets, and mostly outputs debug logs if an error has occurred somewhere in the session
The text was updated successfully, but these errors were encountered:
We have a lot of different trace targets, and we don't have any broad overview of what trace targets someone might want to turn on if they're trying to debug a component or protocol.
We should list all specific log targets, for example some crates have log targets that are different than the crate name or are organized differently than just with crates:
reth/crates/net/network/src/manager.rs
Line 722 in 527d344
reth/crates/engine/tree/src/chain.rs
Line 127 in 527d344
The document should also contain a list of crates that typically do not use targets like this, for example with
reth_eth_wire
:reth/crates/net/eth-wire/src/ethstream.rs
Lines 119 to 122 in 527d344
The docs should try to explain whether or not the log level makes a difference, and what gets logged, for example:
reth_eth_wire
hastrace!
anddebug!
targets. It outputs RLPx session related information withtrace
targets, and mostly outputsdebug
logs if an error has occurred somewhere in the sessionThe text was updated successfully, but these errors were encountered: