Incident Response — Agentic MTTR Demo

INC17837942934957

P3newai_assisted

gateway alert flapping, may already be auto-resolving

Assembled Context — bounded to last 30 minutes
Rolling logs
Recent commits
f9c966f infra: update internal DNS zone for service mesh migration — s.kim
Similar past incidents
(none found)
Diagnosis Agent
ran in parallel
A recent internal DNS zone update for the service mesh triggered transient gateway monitoring flaps, causing the alert to fire and auto‑resolve repeatedly without affecting actual error rates.
  • Recent commits: - f9c966f infra: update internal DNS zone for service mesh migration (s.kim)
  • [gateway] WARN alert fired 90 seconds ago
  • [gateway] INFO alert auto-resolve condition met once, then re-triggered
  • [gateway] INFO current error rate 0.3%, within normal range
  • [gateway] WARN historically this monitor has flapped 6 times in the last 24 hours without real impact
Assessed: P4 / network
Self-reported confidence: 85% (audit-only — not used by the gate)
openai/gpt-oss-120b · 1710ms
Severity / Routing Agent
ran in parallel
P4 / network
Routed to: networking-team
The incident reports an alert flapping on the gateway with an error rate within normal ranges and no active user impact. The history shows frequent false positives, suggesting it is a minor monitoring/noise issue.
Self-reported confidence: 85% (audit-only — not used by the gate)
gemini-flash-lite-latest · 942ms
Scenario Matcher
deterministic, pre-LLM
DNS resolution failures after config change
DNS failures correlated with a recent config/deploy change are best resolved by rolling back the change rather than restarting downstream services.
Match score: 70% · Recommended action: rollback_deploy
Matched tags: dns
Confidence Gate

Computed from 4 measurable signals — not the model's self-reported confidence.

Severity match rate100%
x
Runbook coverage70%
x
Data completeness67%
x
Recency50%
x
Computed confidence (v1)77%
Auto-execute threshold: 75%