arXiv:2607.08529cs.IR2026-07

用符号+神经网络分析日志,1分钟内精准定位微服务故障根源。

Log-Insight: Automating Microservice Incident Diagnosis via Neuro-Symbolic Log Analysis

  • 分六步预处理日志,压缩数百万条记录为精炼证据包
  • 在110次测试中90%以上排名前三即命中真实根因
  • 适合运维工程师快速诊断生产环境故障

在大规模微服务系统中,定位生产事故对SRE至关重要。单次30分钟的事故可生成超两百万行日志,约12亿字符,远超标准LLM上下文窗口,直接使用LLM进行根因分析不可行。现有方法存在缺陷:模板解析缺乏语义异常推理,深度学习检测器输出黑箱二元信号,而LLM流水线则面临上下文溢出和领域幻觉问题。我们提出Log-Insight,一个已在华为生产环境部署的自动化故障诊断系统。核心设计原则是自动化SRE的手动排查流程:符号化阶段模拟熟练工程师的结构化调查——采样、模式理解、模式聚类与统计异常排序。将紧凑且已排序的证据报告交由LLM合成假设报告。六阶段流水线使原始事件减少1000至7000倍,同时保留显著故障信号。在11个历史生产事故(共110次运行,经SRE验证的真实标签)上评估,Log-Insight达到MRR=0.790,90%以上的运行中,正确根因位于前三个假设内,延迟低于一分钟。我们报告了系统性失败模式、主动缓解措施及开放研究方向。取证证据部分——列出精确日志模板与偏移统计——被操作员一致视为关键采纳因素,使系统角色从神秘预言者转变为可信赖的调查助手。

原文摘要 · Abstract (English)

Diagnosing production incidents in large-scale microservice systems is time-critical for Site Reliability Engineers (SREs). A single 30-minute incident window in our deployment can generate over two million log lines--approximately 1.2 billion characters, far exceeding standard LLM context windows--making direct LLM-based Root Cause Analysis (RCA) infeasible. Existing approaches leave gaps: template-based parsers lack semantic anomaly reasoning, deep-learning detectors emit black-box binary signals, and LLM pipelines suffer context overflow and domain hallucination on raw telemetry. We present Log-Insight, an automated incident-diagnosis system deployed in production at Huawei. The core design principle automates the SRE's manual triage workflow: symbolic stages replicate the structured investigation a skilled SRE would perform--sampling, schema understanding, pattern clustering, and statistical anomaly ranking. This hands the LLM a compact, pre-ranked evidence dossier to synthesise into a hypothesis report. Our six-stage pipeline reduces millions of raw events by 1,000-7,000x while preserving statistically significant failure signals. Evaluated on 11 historical production incidents (110 runs, SRE-validated ground truth), Log-Insight achieves MRR = 0.790, returning the correct root cause within the top-3 hypotheses in over 90% of runs in under a minute of latency. We report systematic failure modes, active mitigations, and open research directions. The Forensic Evidence section--listing exact log templates and skew statistics--was consistently identified by operators as a key adoption factor, shifting the system's perceived role from opaque oracle to investigative assistant.

故障诊断日志分析AI运维符号学习

Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。