Skip to content

feat: alert when an instance's fetch keeps failing - #2

Merged
Skeyelab merged 1 commit into
mainfrom
feat/alert-on-failing-fetches
Sep 26, 2026
Merged

Skeyelab merged 1 commit into
mainfrom
feat/alert-on-failing-fetches

Conversation

@Skeyelab

Copy link
Copy Markdown
Member

The stuck checks skip stale data, so a revoked token or an unreachable instance froze every row and sent nothing to the webhook feed.

evaluateStuck now also takes the instance states and emits fetch_failed (resource_type instance, error in detail) once a fetch has been failing past the stuck threshold. It fires once per outage and re-arms on recovery. Documented in the README. Ported from aws-green #56.

Tests: fires once at the threshold with the error in detail, stays quiet while still failing, and alerts again after a recovery and a new outage.

🤖 Generated with Claude Code

The stuck checks deliberately skip stale data, so a revoked API token or an
unreachable Coolify instance froze every row on screen and sent nothing to the
webhook feed. evaluateStuck now also takes the instance states and emits
fetch_failed for an instance whose fetch has been failing past the stuck
threshold, firing once and re-arming on recovery. The error rides in detail so
the payload tells a credential problem from an outage.

Ported from aws-green #56.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Skeyelab
Skeyelab enabled auto-merge (squash) September 26, 2026 15:06
@Skeyelab
Skeyelab merged commit 88f20c8 into main Sep 26, 2026
3 checks passed
@Skeyelab
Skeyelab deleted the feat/alert-on-failing-fetches branch September 26, 2026 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant