TraceOps AI: Building an AI-Powered Service Investigation Agent with FalkorDB and MCP
说明与用途
TraceOps AI 结合 FalkorDB、MCP 和本地 Qwen 模型,快速检索服务、事件和运行手册的关联数据,帮助工程师更高效地调查微服务故障。
问题
Engineers struggle to understand connected operational context when a microservice fails, making it hard to identify impacted services, ownership, incidents, deployments, and runbooks.
结果
The prototype demonstrates that a graph database combined with MCP‑exposed tools and a local LLM can efficiently surface connected operational evidence, reducing investigation time and improving clarity of root‑cause analysis.
工作流
- Receive user question about a service
- Agent interprets request and selects relevant operational data
- MCP tools query FalkorDB for service details, dependencies, ownership, incidents, runbooks, and deployment correlations
- Graph queries traverse relationships, including multi‑hop dependencies
- Agent constructs investigation response using retrieved evidence
- Frontend displays the investigation output to the user
证据
The goal is not to claim that every investigation establishes a definitive root cause. Instead, TraceOps AI aims to help connect relevant evidence and distinguish observed relationships from conclusions that still need verification.
The prototype includes synthetic operational data representing services, teams, incidents, deployments, and runbooks.
For this project, I integrated graph investigation capabilities through the Model Context Protocol (MCP).
- 记录日期: 2026-10-18T14:41:01.997Z