Investigate mechanism to detect peer disconnect event

[iamhsk]

Context

Anecdotally we've been hearing that other Ethereum client nodes are disconnecting Besu nodes. If this is true, this will affect Besu's ability to hear about transactions fast and undermine decentralization and security. However, these have been only anecdotal stories and we don't have a specific incident where we can investigate the root cause. This GH issues is attempting to set up tooling and mechanisms that will help us pinpoint at an event where other peer nodes disconnect from Besu.

Desired Outcome

• Come up with a way to note when non-Besu peer nodes disconnect from Besu canary nodes.
• Store these information on disconnection events somewhere so that we can look back in the future.
• Provide ability to filter through these events so that we are not overloaded with less-meaningful disconnection events (Most clients periodically drop peers for security reasons and these are not what we are interested in investigating)

Note

• Talk to Fabio regarding his idea