lighthouse/validator_client
Michael Sproul c27f2bf9c6 Avoid excessive logging of BN online status (#4315)
## Issue Addressed

https://github.com/sigp/lighthouse/pull/4309#issuecomment-1556052261

## Proposed Changes

Log the `Connected to beacon node` message only if the node was previously offline. This avoids a regression in logging after #4295, whereby the `Connected to beacon node` message would be logged every slot.

The new reduced logging is _slightly different_ from what we had prior to my changes in #4295. The main difference is that we used to log the `Connected` message whenever a node was online and subject to a health check (for being unhealthy in some other way). I think the new behaviour is reasonable, as the `Connected` message isn't particularly helpful if the BN is unhealthy, and the specific reason for unhealthiness will be logged by the warnings for `is_compatible`/`is_synced`.
2023-05-22 02:36:43 +00:00
..
slashing_protection Split common crates out into their own repos (#3890) 2023-04-28 01:15:40 +00:00
src Avoid excessive logging of BN online status (#4315) 2023-05-22 02:36:43 +00:00
Cargo.toml Split common crates out into their own repos (#3890) 2023-04-28 01:15:40 +00:00