You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE] add metric which exposes number of headers/data which did not validate successfully #5
This looks already covered by ev_metrics_submission_failures_total{chain_id, type} (type is header or data). It is incremented only when a block fails all its verification retries (the "max retries exhausted" path in the verifier), which is exactly the semantics asked for here. Alongside it:
ev_metrics_unsubmitted_blocks_total{chain_id, blob_type} and unsubmitted_block_range_start/end show how many blocks, and which ranges, are currently unverified.
ev_metrics_submission_attempts_total is the matching denominator.
Since #57 the counters are per blob type, and since #59 blocks with transactions are verified for both header and data. The name differs from the suggested da_submission_failed; if that exact name matters for existing dashboards, say so. Otherwise this can be closed.
Activity
auricom commentedon Oct 20, 2026
This looks already covered by
ev_metrics_submission_failures_total{chain_id, type}(type isheaderordata). It is incremented only when a block fails all its verification retries (the "max retries exhausted" path in the verifier), which is exactly the semantics asked for here. Alongside it:ev_metrics_unsubmitted_blocks_total{chain_id, blob_type}andunsubmitted_block_range_start/endshow how many blocks, and which ranges, are currently unverified.ev_metrics_submission_attempts_totalis the matching denominator.Since #57 the counters are per blob type, and since #59 blocks with transactions are verified for both header and data. The name differs from the suggested
da_submission_failed; if that exact name matters for existing dashboards, say so. Otherwise this can be closed.