Operations · Advanced
Investigate production incidents and diagnose root causes
Correlate telemetry, logs, and infrastructure state to troubleshoot active alerts
- When something happensAlert notification received
- ThenQuery metrics and inspect pods
- ResultDraft report and fix for approval
When production alerts fire or unexpected errors surge, triage demands rapid correlation across logs, system metrics, and deployment history. This bot inspects telemetry data, runs diagnostic queries against cluster resources, isolates probable root causes, and prepares an incident report alongside proposed remediations.
Prompt to start with
BotBentoRecommended
Analyze incoming production alert payloads and identify affected hosts, pods, or services. Use terminal diagnostics and datadog to pull relevant error traces, event logs, and utilization graphs. Cross-reference recent github deployments to locate changes introduced near the incident start time. Formulate an incident diagnosis detailing the primary failure mechanism and recommended configuration change or rollback. Draft your findings and any proposed code fixes or Slack notifications, but always wait for operator approval before posting messages or opening pull requests.