materialize step 7: freshness alerting + collapsed-bench ttl keep-alive - #422
Merged
Conversation
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
1 participant
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.
Three pieces from the 2026-06-12 silent-freeze postmortem: (1) touchSnapshot refreshes the safety-net TTL when the worker keeps a previous snapshot, so a bench that stays broken keeps its carried data and honest history forever instead of losing it when the blob expires after 2h. (2) The worker pings Slack after 3 consecutive failed heartbeat writes (then hourly) — this exact alert would have fired at 01:05 last night instead of 10 silent hours. (3) The health-check cron (active on prod after the dev->main cutover) watchdogs the heartbeat key and alerts when stale >5min with hourly reminders, covering the worker-process-dead case the worker cannot self-report.