Triage · on-call copilot
When the pager goes off, Triage already knows.
Triage matches every alert against your incident memory, inspects the code path with read-only access, and proposes a fix with reasoning. You verify and apply.
4 pending1 resolved today
Live alert feed
5 alerts · last 24hPagerDuty · 02:14P1
payment_retry_p99 > 8s for 5m
Confidence91%
Triage hypothesis
Retry storm hitting Stripe webhooks. Same pattern as incident #14 (Aug 2025).
- →Same alert pattern fired 02:14 → 03:40 on 2025-08-19
- →Recent deploy: PR #178 (payment retry refactor) merged 18h ago
- →Code path: server/payments/retry.ts:42 — backoff disabled by feature flag
Proposed fix
server/payments/retry.tsRe-enable exponential backoff in retry config
- max_attempts: 5, - backoff_ms: 0, + max_attempts: 5, + backoff_ms: 250, + backoff_strategy: 'exponential',
Saves: 2am panic → 5-min recovery
Connected alert sources
Anything that pages someone gets piped into Triage.
PagerDutySentryDatadogGitHub ActionsOpsgenie· connectHoneycomb· connectCloudWatch· connect
Code access · the contract
Read-only. Per-repo. Engineer applies, never auto-merges.
- Read-only by default
- Per-repo opt-in
- Diff-only output
- Engineer verifies + applies, always
- Audit log of every read
How Triage closes the loop
Alert → match → inspect → propose → human approve.
- STEP 1Alert landsWebhook from PD/Opsgenie/Sentry. Parsed + classified.
- STEP 2Match memorySearch incident history + recent PRs in the same area.
- STEP 3Inspect codeRead-only access. Pulls the file(s) the alert path touches.
- STEP 4Draft fixLLM proposes a diff with reasoning + citations. Confidence score.
- STEP 5Human approvesOn-call reviews diff. Approves, rejects, or defers.
Why Triage isn’t just another AIOps tool
The space is heating up. Here’s where we’re different.
| Tool | What they do | Where they stop |
|---|---|---|
| PagerDuty / Opsgenie | Route the page | No analysis, no fix |
| Datadog Watchdog / Honeycomb | Anomaly detection | Tell you something’s wrong, not why |
| Rootly / FireHydrant | Incident management | Ticket the incident; humans triage |
| Resolve / Cleric / Parity | Runbook automation, basic AI triage | Don’t inspect code; no fix diff |
| Throughloop Triage | Match memory + inspect code + propose diff | — |