triage-alerts

Correlate Gatus failing endpoints with Alertmanager alerts to identify root causes.

Updated Sep 18, 2025
One-click install
npx skills add https://github.com/david-driscoll/home-operations --skill triage-alerts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-alerts
Source: https://github.com/david-driscoll/home-operations/tree/main/.github/skills/triage-alerts
Command: npx skills add https://github.com/david-driscoll/home-operations --skill triage-alerts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you rapidly triage operational incidents by correlating live uptime failures from Gatus with active alerting signals from Alertmanager, then translating those patterns into actionable root-cause hypotheses and remediation steps.

Core Features & Use Cases

  • Live failure discovery: Pulls current failing endpoint statuses from Gatus and active alerts from Alertmanager.
  • Root-cause patterning: Categorizes issues into likely causes (e.g., ingress/auth failures, DNS/webhook mismatches, rollout stalls, crash loops, secret sync problems, HelmRelease rollback loops).
  • Cluster-specific verification and remediation: Recommends kubeconfig-appropriate commands to inspect Helm/Kustomize health, pod/event state, and apply targeted fixes.
  • Common remediation playbooks: Includes concrete actions such as breaking stuck HelmRelease conditions, forcing ExternalSecret resync, triggering Flux reconciles, and restarting/rescheduling workloads.
  • Verification loop: Guides polling Gatus until failing endpoints recover to zero.

Quick Start

Run the triage process to fetch Gatus failing endpoints and Alertmanager active alerts, then follow the remediation steps until the failing count reaches 0.

Frequently Asked Questions about triage-alerts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose Kubernetes alert failures and find the root cause?

Diagnose Kubernetes alert failures by correlating failing Gatus endpoint signals with active Alertmanager alerts, then grouping them into root-cause buckets like crash loops or rollout stalls using defined heuristics.

What is the best way to triage Alertmanager alerts with Gatus endpoint failures?

Triage Alertmanager alerts with Gatus by fetching and filtering live HTTPS endpoint failures and active alerts, categorizing them into operational patterns like DNS reachability or Helm reconciliation issues.

How do I fix stuck HelmRelease and Flux reconciliation loops in Kubernetes?

Fix stuck HelmRelease and Flux reconciliation loops by executing kubeconfig-scoped inspection commands to identify the stall, breaking stuck conditions, and triggering targeted Flux reconciles to validate recovery.

Can I use this to troubleshoot Kubernetes crash loops and ExternalSecret synchronization errors?

Yes, you can troubleshoot Kubernetes crash loops and ExternalSecret synchronization errors by correlating uptime failures with active alerts, then forcing ExternalSecret resyncs and restarting affected workloads.

How do I verify incident remediation and confirm alert recovery?

Verify incident remediation by executing safe kubeconfig-scoped commands to apply fixes, then guide a verification loop polling Gatus until the count of failing endpoints reaches zero.

Why does my Kubernetes forward-auth reverse proxy alert keep firing?

Your Kubernetes forward-auth reverse proxy alert may keep firing due to ingress or authentication failures identified by correlating Gatus endpoint signals with Alertmanager conditions to pinpoint the root cause.