observability: instant_email_failover_total alert + tile + catalog (#35)#54
Merged
Merged
Conversation
Companion to worker #35 (failover ESP provider). Rule 25 — every new metric ships its alert + dashboard tile + catalog row. Metric: instant_email_failover_total{outcome} emitted by the worker FailoverProvider (worker/internal/email/failover_provider.go). Inert when EMAIL_PROVIDER_FALLBACK is unset (lazy CounterVec, never emits in single-provider mode). - prometheus-rules: new instant-worker-email-failover group — EmailFailoverEngaged (P1, fallback_ok rate > 0 for 10m = primary ESP degraded, secondary carrying load) and EmailFailoverAllFailed (P0, all_failed rate > 0 for 5m = every ESP refused, email being lost). - newrelic/alerts: email-failover-engaged.json (P1), email-failover-all-failed.json (P0). Mirror the Prom thresholds. - dashboard: "Email failover outcomes (1h)" line tile faceted by outcome. - METRICS-CATALOG: row for instant_email_failover_total (lazy, owner worker, alerts + tile cross-referenced). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mastermanas805
added a commit
that referenced
this pull request
Jun 5, 2026
…#54) (#55) Rule 25 artifacts for instant_deploy_scaled_to_zero_total{outcome} + instant_deploy_idle_apps (emitted by worker/internal/jobs/deploy_idle_scaler.go). - Prom rules (instant-worker-deploy-scale-to-zero group): DeployScaleToZeroWakeFailed (wake_failed > 0 / 15m → P1: app stuck asleep), DeployScaleToZeroScaleDownFailures (scale_failed >= 5 / 30m → P2: savings not landing, no customer impact). - NR alert: deploy-scale-to-zero-fail.json (wake_failed → CRITICAL). - Dashboard: two tiles on instanode-reliability.json — asleep-apps billboard + scale-outcome stacked-bar. - METRICS-CATALOG.md: rows for the counter (lazy, 4 outcomes primed) + the gauge (eager). All INERT until an operator sets DEPLOY_SCALE_TO_ZERO_ENABLED — the series stay 0 and the alerts stay quiet until the feature is canaried on. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Rule-25 companion to worker PR InstaNode-dev/worker#93 (failover ESP provider). Every new metric ships its alert + dashboard tile + catalog row.
Metric:
instant_email_failover_total{outcome}emitted by the workerFailoverProvider. Inert whenEMAIL_PROVIDER_FALLBACKis unset (lazy CounterVec — never emits in single-provider mode).Artifacts
instant-worker-email-failovergroup —EmailFailoverEngaged(P1:fallback_okrate > 0 for 10m → primary ESP degraded, secondary carrying load)EmailFailoverAllFailed(P0:all_failedrate > 0 for 5m → every ESP refused, email lost)email-failover-engaged.json(P1),email-failover-all-failed.json(P0) — mirror the Prom thresholds.outcome.instant_email_failover_total.All JSON + YAML validated.
🤖 Generated with Claude Code