Abhiram1442

Incident Triage Agent — DevOps skill for Claude Code

DevOps community

An AI-powered agent built with AWS Bedrock, Claude, and Strands Agents SDK that monitors system alerts, connects related signals, finds potential root causes, checks metrics for evidence, assigns seve.

How to install Incident Triage Agent

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Abhiram1442/incident-triage-agent and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Incident Triage Agent does

An AI-powered agent built with AWS Bedrock, Claude, and Strands Agents SDK that monitors system alerts, connects related signals, finds potential root causes, checks metrics for evidence, assigns severity, and automatically creates structured incident tickets to reduce MTTR and alert fatigue.

Alternatives in DevOps

  • Unifly Status — Quick health check of UniFi infrastructure 248 ★
  • Spec Kit Plus — A practical fork of github/spec-kit with patterns & templates for building scalable multi-agent AI systems 220 ★
  • Claude In The Box — Use Anthropic Claude Agent SDK in a Cloudflare Sandbox 88 ★

README

Autonomous Incident Triage Agent

An autonomous AI agent that monitors system alerts, correlates related signals, identifies root causes, and automatically creates structured incident tickets.

**Built with:** AWS Bedrock, Claude via Bedrock, Strands Agents SDK

Setup

python -m venv venv
source venv/bin/activate
pip install strands-agents boto3

Run

# Local logic test (no API)
python test_logic.py

# Full agent with Bedrock (requires AWS credentials)
python main.py

How it works

  1. Fetches recent alerts from monitoring
  2. Groups alerts by timing & service dependencies
  3. Pulls metrics to confirm hypotheses
  4. Creates incident tickets with evidence-based root cause analysis

Files

  • mock_alerts.py — Sample alert & metric data
  • tools.py — Agent tool definitions
  • main.py — Strands agent with Bedrock integration
  • test_logic.py — Local logic verification (no API)

Demo Output

The agent correctly:

  • Groups A1, A2, A3 as one incident (checkout-api + checkout-db DB pool exhaustion)
  • Isolates A4 as noise (unrelated auth-service event)
  • Cites metric evidence: db_pool_used: 98%, connections: 98/100
  • Assigns high severity due to connection pool type