FaulT-Bench: Towards Benchmarking Network Troubleshooting LLM Agents under Unreliable User Tickets 待解读

下载

新用户看这篇论文该怎么开始

  1. 先点「赞助解读」,AI 会把论文转成可直接执行的行动清单。
  2. 看完“可执行改进行动”后,可快速决定是否值得立项。
  3. 用上面的卡片内容直接发给团队,减少重复阅读。
先订阅关键词,后续不再手工筛论文

摘要

LLM-based agents are increasingly proposed for network fault diagnosis, but existing benchmarks evaluate them only on accurate tickets and always assume a fault is present, conditions rarely met in practice. We present FaulT-Bench, a benchmark of 200 troubleshooting scenarios across eight network topologies, five reimplemented from public practitioner labs, spanning genuine faults, false fault reports, incorrect device attribution, and incorrect root-cause claims. To isolate how ticket wording affects diagnosis, we further rewrite 72 false-premise tickets into five reporter personas that vary reporter confidence and verifiable detail one factor at a time, holding the network state fixed. Our automated harness deploys each scenario in Kathará, lets agents interact through the NIKA tool interface, and scores free-text diagnoses with an LLM judge across outcome, fix, and reasoning quality. Evaluating SADE, ReAct, and Claude Code, we find all three are near-saturated on accurate tickets and robust to misdirection, yet degrade sharply when the network is healthy and the ticket is wrong, probing until a benign condition can be promoted to a root cause rather than concluding nothing is wrong. Persona rewrites show that how a ticket is written matters more than what it claims: a confidently wrong report is handled about as well as an accurate one, while a vague, underspecified report degrades performance sharply. The three agents also fail differently, from constant over-diagnosis to unanswered runs, at very different cost. These results position FaulT-Bench as a benchmark for developing agentic systems that can reason reliably over the noisy, unreliable tickets of real-world network troubleshooting.

分析报告

暂无报告。点击“分析”开始生成。

个性化解读 与社区共享解读不同

用自己的话告诉 AI 你想要什么样的解读(比如"用大白话讲给非专业人士听"、"重点分析对我们团队 RAG 系统的可迁移性"),生成一份只属于你自己的版本;生成后也可以选择设为"愿意共享",被更多人看到、点赞。