Paul Hauner c3e5053612 Reduce false positive logging for late builder blocks (#4073) ... ## Issue Addressed NA ## Proposed Changes When producing a block from a builder, there are two points where we could consider the block "broadcast": 1. When the blinded block is published to the builder. 2. When the un-blinded block is published to the P2P network (this is always *after* the previous step). Our logging for late block broadcasts was using (2) for builder-blocks, which was creating a lot of false-positive logs. This is because the builder publishes the block on the P2P network themselves before returning it to us and we perform (2). For clarity, the logs were false-positives because we claim that the block was published late by us when it was actually published earlier by the builder. This PR changes our logging behavior so we do our logging at (1) instead. It also updates our metrics for block broadcast to distinguish between local and builder blocks. I believe the metrics change will be natively compatible with existing Grafana dashboards. ## Additional Info One could argue that the builder *should* return the block to us faster, however that's not the case. I think it's more important that we don't desensitize users with false-positives.		2023-03-17 00:44:03 +00:00
..
src	Reduce false positive logging for late builder blocks (#4073)	2023-03-17 00:44:03 +00:00
Cargo.toml	Update Mock Builder for Post-Capella Tests (#3958)	2023-02-10 13:30:14 -06:00