DevOps War Room

What does DevOps War Room do?

DevOps War Room is a 3-bot incident response team for Slack. An Incident Commander receives all alerts and requests, classifies severity, and routes to either a Log Analyzer (for error diagnosis via Sentry) or a Deploy Bot (for releases and rollbacks via GitHub + Railway).

When a Sentry alert fires at 3 AM, the team is already working on it.

What's included

3 pre-configured bots:

• Incident Commander — Classifies severity (P0–P4), coordinates response, notifies on-call
• Log Analyzer — Queries Sentry for stack traces, error frequency, affected users, and root cause
• Deploy Bot — Handles deployments, rollbacks, CI status checks, and release management

2 keyword routing rules + 1 fallback:

• Error alerts (error, exception, sentry, crash, 500, timeout) → Log Analyzer
• Deploy requests (deploy, rollback, release, ci, pipeline, hotfix) → Deploy Bot
• Everything else → Incident Commander

4 MCP integrations: Slack, Sentry, GitHub, Railway

How it works

The Incident Commander acts as the central coordination point. When it detects error-related keywords, it delegates to the Log Analyzer which pulls real data from Sentry — stack traces, error counts, affected user counts. For deployment requests, it routes to the Deploy Bot which checks CI status on GitHub before executing.

Every routing decision is logged in the delegation audit trail for post-mortem review.

When to use this template

• You run services that need fast incident response
• You use Sentry for error tracking and GitHub for CI/CD
• You want automated severity classification and routing
• You need a clear audit trail for post-mortems