It must be easy to profile/understand “what is my node currently doing?”, and "where my bandwidth is going?"

• Reintroduce Filtered Logging #8752
  • This is "trivially" done as the filtering was removed in v0.35.x
• metrics: remove peer id label from p2p metrics to prevent cardinality explosion. #2600. Solution not clear (see discussion)
  • Agree on the best tradeoff [Estimation 2 days]
  • Implementation [Estimation 5 days]
• Ask node operators/validators what information and/or tools are currently missing in terms of logging/monitoring.
  • Rework this item once we have their answers (list of issues)
• Audit logging across all packages and determine whether the logs are useful/necessary and whether they're at the correct level (info, debug, error).
  • Starting point: Reduce P2P logging spam [130 logs, estimation 5 days]
  • Other packages [Estimations proportional to the number of logs]
    • Consensus, 253 logs
    • rpc, 90 logs
    • cmd, 60 logs
    • light, 51 logs
    • libs, 49 logs
    • node, 47 logs
    • statesync, 46 logs
    • tools, 36 logs
    • logging improvements: blocksync module #9920
    • abci, 33 logs
    • evidence, 32 logs
    • mempool, 29 logs
    • state, 23 logs
    • other (privval, types,proxy), 33 logs
• Improve Metrics Collection
  • metrics: transition all metrics to using metricsgen generated constructors.  #8488
  • scripts/metricsgen: add the initial version of metricsgen #8479
• How transactions spread using Mempool and Block parts?
  • Log hash of transactions received at mempool and as block parts to determine the duplication of transaction data. Will be useful in determining gains of in solving Compact Block Propagation #7932
• p2p: fix logspam #9756
• node: wire up logger to mempool reactor #9885