Correlate Prometheus metrics and Loki logs to determine alert root causes.
npx skills add https://github.com/damacus/agent-skills --skill alert-investigator
Please help me install this Agent Skill. Skill: alert-investigator Source: https://github.com/damacus/agent-skills/tree/main/skills/alert-investigator Command: npx skills add https://github.com/damacus/agent-skills --skill alert-investigator
Expert Site Reliability Engineer (SRE) specialized in deep-dive investigation of firing infrastructure alerts. Use this agent whenever Alertmanager or Grafana alerts are active and you need a comprehensive root-cause analysis. It should be used to investigate firing alerts by correlating Prometheus metrics and Loki logs, detecting error patterns, analyzing slow requests, and inspecting Kubernetes resource states to provide actionable remediation steps.
Identify an active firing alert and begin a deep-dive investigation using Grafana/Prometheus/Loki data.
High-intent search queries and answers about installing and using this skill.
Investigating firing alerts involves querying Prometheus for metrics and Loki for logs to detect error patterns, analyze slow requests, inspect Kubernetes resource states, and produce actionable remediation steps to restore service health.
Root-cause analysis for active alerts is a structured workflow that triages firing alerts using their annotations, correlates metrics, logs, traces, and Kubernetes state, and outputs a detailed investigation report with concrete remediation steps.
Yes, you can correlate Loki logs with Prometheus metrics during an incident by querying both data sources to detect error patterns and analyze slow requests, inspecting Kubernetes state, and generating a comprehensive investigation report.
It works with Grafana alerting setups by utilizing Grafana, Prometheus, and Loki tooling such as list_alert_rules, query_prometheus, and query_loki_logs to identify active alerts and perform end-to-end deep-dive investigations.
The best way to triage active alerts is to apply a structured workflow that identifies firing alerts, analyzes their annotations, and correlates Prometheus metrics, Loki logs, traces, and Kubernetes state to determine root causes and provide remediation guidance.
You get actionable remediation steps for firing alerts by performing an end-to-end investigation that analyzes Prometheus metrics, Loki logs, traces, and Kubernetes resource states to determine the root cause and restore service health.
timequitySet up Prometheus, Grafana, Loki, and Jaeger for Kubernetes observability.
hamzashakoor119Diagnose Kubernetes pod crashes and deployment issues with kubectl commands.
jg-chalk-ioCollect metrics, logs, and traces from Kubernetes microservices using Prometheus, Grafana, Loki, OpenTelemetry, and Jaeger.
ChatAndBuildAutomate observability stack design with Prometheus metrics, OpenTelemetry tracing, and SLI/SLOs.
