Add get_payload_delivery_failure metric for relay-side misses - #790
Merged
Conversation
Introduce a `get_payload_delivery_failure` counter with a `reason` label
to track slots where the relay committed a bid via getHeader but then
failed to fulfill the payload in getPayload. This isolates genuine
relay-side failures from the existing get_payload_count{status="error"},
which conflates them with proposer-side faults.
Reasons counted:
- payload_not_found: an eligible bid existed but the execution payload
was gone/unreadable, or a datastore error occurred during retrieval
- publish_failed: all beacon nodes failed to publish the block
(incremented in both the V1 synchronous and V2 async publish paths)
- internal_error: could not build the beacon block from our own payload
Proposer-side faults are deliberately excluded (bad signature, sent too
late, duplicate/already-delivered, wrong relay, below-floor bids), so the
metric reflects only failures the relay is responsible for.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: bakhtin <a@bakhtin.net>
dvush
approved these changes
Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce a
get_payload_delivery_failurecounter with areasonlabel to track slots where the relay committed a bid via getHeader but then failed to fulfill the payload in getPayload. This isolates genuine relay-side failures from the existing get_payload_count{status="error"}, which conflates them with proposer-side faults.Reasons counted:
Proposer-side faults are deliberately excluded (bad signature, sent too late, duplicate/already-delivered, wrong relay, below-floor bids), so the metric reflects only failures the relay is responsible for.
📝 Summary
⛱ Motivation and Context
📚 References
✅ I have run these commands
make lintmake test-racego mod tidyCONTRIBUTING.md