apollo_dashboard: widen l1_message_no_successes alert window to 15m#14318
apollo_dashboard: widen l1_message_no_successes alert window to 15m#14318ShahakShama wants to merge 1 commit into
Conversation
PR SummaryLow Risk Overview This is meant to cut false-positive pages after sequencers moved to a single L1 provider, where short provider blips can look like “no successes” in a 5m window even when scraping recovers quickly. Reviewed by Cursor Bugbot for commit d04044d. Bugbot is set up for automated code reviews on this repo. Configure here. |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Goal: reduce false-positive pages on the L1 message scraper alert. Since each sequencer moved to a single L1 provider, the `l1_message_no_successes` alert (no successful scrapes within the window) fires spuriously: a brief gap from the sole provider trips it even though scraping recovers shortly after. Widening the evaluation window from 5m to 15m tolerates these short gaps. Change: bump the `increase(l1_message_scraper_success_count[...])` range from 5m to 15m in the alert definition, and regenerate the matching expression in dev_grafana_alerts.json. Follow-up (not in this PR): revert to 5m once a fallback mechanism that switches back to a specific provider per sequencer is in place. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
b7d888d to
d04044d
Compare
dan-starkware
left a comment
There was a problem hiding this comment.
@dan-starkware reviewed 2 files and all commit messages, and made 1 comment.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on ShahakShama).

Goal: reduce false-positive pages on the L1 message scraper alert.
Since each sequencer moved to a single L1 provider, the
l1_message_no_successesalert (no successful scrapes within thewindow) fires spuriously: a brief gap from the sole provider trips it
even though scraping recovers shortly after. Widening the evaluation
window from 5m to 15m tolerates these short gaps.
Change: bump the
increase(l1_message_scraper_success_count[...])range from 5m to 15m in the alert definition, and regenerate the
matching expression in dev_grafana_alerts.json.
Follow-up (not in this PR): revert to 5m once a fallback mechanism
that switches back to a specific provider per sequencer is in place.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com