Node logs: remove block properties (timestamp and fitness)
Jan 6 14:33:10.920 - validator.chain: Update current head to BLkhtA81uak1SxxCDCVMXEnXCKsJcFLajVT84ZjrFKbxAaJUL4E
Jan 6 14:33:10.920 - validator.chain: (level 462824, timestamp 2023-01-06T13:33:10-00:00, fitness
Jan 6 14:33:10.920 - validator.chain: 02::00070fe8::::ffffffff::00000000), same branch
In some events advertizing new blocks, some properties are seen as obscure, and can even be found from elsewhere, like the fitness
or the timestamp
. Also they are probably not greppable, not especially useful for a developper. (Could the fitness be replaced by priority instead ?)
-
timestamp
- Regarding the Update current head to message, I think it worth keeping the timestamp. Indeed, it is easy to know if your node is "up to date" while looking at it (if last block timestamp is very recent). The level requires a third party to get the "is my node synced" information.
- we could replace by
4ms ago
which is shorter than `timestamp 2023-01-06T13:33:10-00:00 - we keep only one unit (year month s ms )
- is there a case where the timestamp is very different from the log date ?
- don't display timestamp if close to current date ?
-
fitness: ensure if useful or not (feedback: + Albin Romain), fitness can be found with the block hash.