After some exchange with @g11tech we (re-)discovered that the client is not reporting any peer/networking stats (any more?) after merge, at least not on the INFO debug level.
This should change, if there is pre-Merge reporting this should optimally be aligned/consolidated to avoid code redundancy here. I guess most adequate reporting is in some interval cadence as being done for the caches and other things.
(so main thing here is that one has absolutely no overview if and how many peers the client currently has. When writing this: maybe the above reporting can/should also be complemented by a "all peer connections lost" warning when client is going from >=1 to 0 peers)
After some exchange with @g11tech we (re-)discovered that the client is not reporting any peer/networking stats (any more?) after merge, at least not on the
INFO
debug level.This should change, if there is pre-Merge reporting this should optimally be aligned/consolidated to avoid code redundancy here. I guess most adequate reporting is in some interval cadence as being done for the caches and other things.
(so main thing here is that one has absolutely no overview if and how many peers the client currently has. When writing this: maybe the above reporting can/should also be complemented by a "all peer connections lost" warning when client is going from >=1 to 0 peers)