Move detailed peer logging to debug, add diversity

[benaadams]

Changes

• Move detailed (line per peer) to Debug
• Add diversity to single line logs

2023-06-09 06:42:15.8209|Allocated sync peers 72(72)/100 | Geth (51.39 %), Nethermind (30.56 %), erigon (13.89 %), besu (2.78 %), Unknown (1.39 %)
2023-06-09 06:42:30.9419|Peers | with known best block: 71 | all: 71 | Geth (52.11 %), Nethermind (30.99 %), erigon (14.08 %), besu (2.82 %)

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Logging changes

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

[LukaszRozmej]

One thing I am lacking here is some summary of allocation types. Could be good for diagnosing syncing issues.

[benaadams]

One thing I am lacking here is some summary of allocations. Couild be good for diagnosing syncing issues.

Not sure what you mean? Could you provide example?

[LukaszRozmej]

One thing I am lacking here is some summary of allocations. Couild be good for diagnosing syncing issues.

Not sure what you mean? Could you provide example?

Summary of this column

[benaadams]

One thing I am lacking here is some summary of allocation types. Could be good for diagnosing syncing issues.

Added

Allocated sync peers 55(55)/100 | Active: None | Sleeping: All | Geth (47.27 %), Nethermind (32.73 %), Erigon (20.00 %)

Will get example from syncing when do it again