Eight services alerting, one cause: building AI on-call agents on a graph
说明与用途
基于 FalkorDB 图的 AI 代理通过查询服务依赖、所有者、最近更改和过去事件,加速根本原因识别。
问题
When multiple services alert simultaneously, identifying the single root cause is hard because alerts are scattered across unrelated services.
结果
The system reduces root‑cause identification time, eliminates missed causes, and stores incident knowledge for future reuse.
工作流
- 1. Collect alerting component names.
- 2. Run root‑cause Cypher query to find components common to alerting services.
- 3. Rank results by coverage, alerting status, dependency alerting, and recent changes.
- 4. Present top candidates to the investigator agent.
- 5. Verify candidate with a coverage check; if a better candidate exists, iterate once.
- 6. Record incident, postmortem, and lesson in the graph.
- 7. On next incident, use vector‑search + graph to find similar past incidents.
证据
Eight alerts, and only one of them is the actual problem.
None of those answers sits in one place. They're in the connections.
I built the agents on a graph.
The ordering reads the way an SRE thinks: covers, is_alerting, alerting_deps, recent_changes.
- 记录日期: 2026-10-18T06:41:21.520Z