synthetic-traffic: page Discord when ticks fail persistently - #146
Merged
Conversation
Bootstrap and reconcile throws never reached any alert path, so a wedged engine was invisible until someone read the Fly logs. The run loop now alerts after 3 consecutive failed ticks, re-alerts hourly while stuck, and notes recovery.
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.
Problem
The libdbus brick (#145) was Discord-silent for hours: bootstrap/reconcile throws land in the run loop's catch, which only
console.errors. The existing alerts (all-actions-failed batch, low runway, network reset) never see them, so a wedged generator is invisible without reading Fly logs, and the promised "MELI formed" ping never arrives.Fix
The run loop now tracks consecutive failed ticks and pages the existing
discordAlertpath:A lone failed tick stays log-only (routine testnet noise).
discordAlertalready no-ops without the webhook env (local proving) and never throws.Verified
deno check,deno lint,deno fmt --checkclean onsynthetic-traffic/main.ts. Streak logic: failures 1-2 log only; 3rd alerts; re-alerts at 15, 27, ...; success after an alerted streak sends the recovery note and resets.