← Latest papers
🤖 AI

Collaborative AI Agents and Critics for Fault Detection and Cause Analysis in Network Telemetry

This paper proposes a federated multi-agent system where private AI agents and critics collaboratively optimize multimodal tasks like network fault detection through a central server without inter-agent communication, achieving convergence guarantees with communication overhead independent of the number of agents.

Original authors: Syed Eqbal Alam, Zhan Shu

Published 2026-04-02
📖 5 min read🧠 Deep dive

Original authors: Syed Eqbal Alam, Zhan Shu

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you run a massive, high-tech factory called "The Network." This factory is constantly producing data (like traffic reports, sensor readings, and logs). Sometimes, things go wrong: a machine breaks, a pipe leaks, or a conveyor belt jams. These are "faults."

Your goal is to find these faults instantly, figure out how bad they are, and understand why they happened. But you can't do it alone; you need a team.

This paper proposes a new way to organize that team using AI Agents (the workers) and AI Critics (the quality inspectors), all working together under a Central Manager.

Here is the breakdown of their system, explained simply:

1. The Cast of Characters

  • The AI Agents (The Workers): These are the doers. They look at the data and try to solve the problem. Some workers are "Old School" (using fast, traditional math like XG-Boosting), while others are "New School" (using fancy Generative AI like Llama or Mistral that can write and reason).
  • The AI Critics (The Inspectors): These are the reviewers. They don't do the initial work; they wait for the Agents to finish, read their answers, and give feedback. They ask: "Is this right? Is it clear? Did you miss anything?" They can give a score (like a grade out of 10).
  • The Central Server (The Manager): This is the boss. It doesn't do the work itself. Instead, it counts how many workers and inspectors are currently busy. If too many people are working on one task, it tells some to take a break. If too few are working, it calls more to action.

2. How They Work Together (The Dance)

Imagine a relay race where the runners (Agents) and judges (Critics) are trying to find the perfect number of people to run at any given moment.

  1. The Task: A user asks a question (e.g., "Is this network connection broken?").
  2. The Worker Steps Up: An AI Agent decides, "I'll take this!" It uses its brain (either traditional math or a Large Language Model) to generate an answer.
  3. The Inspector Checks: The Agent sends the answer to an AI Critic. The Critic reads it.
    • If the Critic says: "This is great, score 9/10," the Agent sends the answer to the user.
    • If the Critic says: "This is weak, score 4/10," the Agent says, "Okay, I'll try again," and rewrites the answer based on the feedback.
  4. The Manager Adjusts: The Central Server watches everyone. It doesn't know what the Agents are thinking or how they calculate their costs (privacy is key!). It only sees who is active.
    • If too many Agents are working on "Text" tasks, the Manager sends a signal to slow them down.
    • If not enough Agents are working on "Image" tasks, the Manager signals them to speed up.

3. The Secret Sauce: "Stochastic Approximation"

This is the fancy math part, but think of it like tuning a radio.

Imagine you are trying to find the perfect station. You turn the dial a little bit, listen, and if it's fuzzy, you turn it a tiny bit more. You keep doing this until the sound is crystal clear.

  • The Agents and Critics are constantly "tuning" their willingness to work.
  • They use a special math trick called Multi-Time Scale Stochastic Approximation.
    • Fast Scale: They react quickly to immediate feedback (like the Critic's score).
    • Slow Scale: They slowly adjust their long-term habits (like deciding to work more often on Tuesdays).
  • The Result: Over time, the system naturally settles into the "Goldilocks Zone"—not too many workers, not too few, just the right amount to get the job done with the least amount of wasted energy (cost).

4. The Real-World Test: Network Telemetry

The authors tested this system on a real-world problem: Network Telemetry. This is like a doctor's monitor for a computer network. It tracks data flow, errors, and speed.

  • The Data: They used a dataset with 99 different columns of data (like "bytes sent," "errors," "bandwidth") and log files.
  • The Experiment:
    • Fault Detection: They asked the system to find broken connections.
      • Result: The "Old School" workers (XG-Boosting) were faster and more accurate at just spotting the error. They were like a metal detector: fast and precise.
      • The "New School" workers (Generative AI) were a bit slower and made more mistakes at just spotting the error, but they were better at explaining why.
    • Severity & Cause Analysis: They asked the system to explain why the error happened and if it was a big deal.
      • Result: Here, the "New School" workers (Generative AI) shined. They could read the logs and say, "This looks like a cable was unplugged, and it's a critical failure," or "This is just a heavy traffic jam, not a big deal."

5. Why Is This Important?

  • Privacy: The workers and inspectors never have to share their secret formulas (cost functions) with each other or the manager. They just share their "willingness to work."
  • Scalability: The system works great whether you have 10 workers or 10,000. The communication cost stays low because the Manager only broadcasts simple signals, not huge data files.
  • Adaptability: It can handle different types of tasks (text, images, video, sensor data) all at once without getting confused.

The Bottom Line

This paper describes a self-organizing AI team. Instead of a human boss micromanaging everyone, the team uses a clever feedback loop to figure out exactly how many people should be working on a task at any given second.

It's like a jazz band where the musicians (Agents) and the conductor (Server) communicate through subtle cues rather than sheet music, eventually finding the perfect rhythm to solve complex problems like network failures, all while keeping their individual musical styles (algorithms) private.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →