Skip to content

head-lag: raise aberrant-value cap to 120s #1022

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Flotapponnier merged 1 commit into from
Jul 9, 2026
Merged

head-lag: raise aberrant-value cap to 120s #1022

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions harnesses/aggregator-head-lag/cmd/script/metrics.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -383,8 +383,12 @@ func RecordMetadataLatency(provider string, chain string, latencyMs float64, reg

// RecordHeadLag records the head lag for an aggregator on a specific chain
func RecordHeadLag(aggregator string, chain string, lagBlocks int64, lagSeconds float64, region string, txHash string) {
// Filter out aberrant values (> 30s likely means connection issues, not real lag)
if lagSeconds < 0 || lagSeconds > 30 {
// Filter out aberrant values. 120s matches the fast-trade filter: it
// keeps out reconnect replay backlogs (minutes-old events redelivered
// after a resubscribe) while letting real high lag through. The old 30s
// cap silently dropped every codex sample on Robinhood Chain (~45s real
// lag), showing "no data" instead of the honest bad number.
if lagSeconds < 0 || lagSeconds > 120 {
return
}

Expand Down
Loading