Collaborative AI Agents and Critics for Fault Detection and Cause Analysis in Network Telemetry
Organizations: Department of Electrical and Computer Engineering, University of Alberta, Edmonton, Alberta, Canada · SheQAI Research, Edmonton, Alberta, Canada
Abstract
We develop algorithms for collaborative control of AI agents and critics in a multi-actor, multi-critic federated multi-agent system. Each AI agent and critic has access to classical machine learning or generative AI foundation models. The AI agents and critics collaborate with a central server to complete multimodal tasks such as fault detection, severity, and cause analysis in a network telemetry system, text-to-image generation, video generation, healthcare diagnostics from medical images and patient records, etcetera. The AI agents complete their tasks and send them to AI critics for evaluation. The critics then send feedback to agents to improve their responses. Collaboratively, they minimize the overall cost to the system with no inter-agent or inter-critic communication. AI agents and critics keep their cost functions or derivatives of cost functions private. Using multi-time scale stochastic approximation techniques, we provide convergence guarantees on the time-average active states of AI agents and critics. The communication overhead is a little on the system, of the order of , for modalities and is independent of the number of AI agents and critics. Finally, we present an example of fault detection, severity, and cause analysis in network telemetry and thorough evaluation to check the algorithm's efficacy.
Figures & tables
| Models | Accuracy | Precision | Recall | F1-Score |
| Agents with XG Boosting | 0.9644 | 0.9397 | 0.9929 | 0.9656 |
| Agents and Critics enabled with Llama3.2 (with RAG) | 0.5882 | 0.8000 | 0.6154 | 0.6957 |
| Agents and Critics enabled with Llama3.2 (without RAG) | 0.4612 | 0.4027 | 0.6648 | 0.5016 |
| Models | Actor | Query | Severity | Cause Summary |
| Llama3.2 | 24. Predict whether Device with ‘name’: ‘Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/data-rate’, ‘time’: ‘2017-09-01 10:23:18.222000’, ‘EncodingPath’: ‘Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/data-rate’, ‘Producer’: ‘leaf3’, ‘bandwidth’: ‘100000000.0’, ‘input-data-rate’: ‘10261058.0’, ‘input-load’: ‘26.0’, ‘input-packet-rate’: ‘166870.0’, ‘interface-name’: ‘HundredGigE0/0/0/5’, ‘load-interval’: ‘0.0’, ‘output-data-rate’: ‘10482276.0’, ‘output-load’: ‘26.0’, ‘output-packet-rate’: ‘449830.0’, ‘peak-input-data-rate’: ‘0.0’, ‘peak-input-packet-rate’: ‘0.0’, ‘peak-output-data-rate’: ‘0.0’, ‘peak-output-packet-rate’: ‘0.0’, ‘reliability’: ‘255.0’ has a Critical fault or Non-critical fault. | Non-critical | The device experienced a sudden decrease in input data rate due to a likely temporary network performance issue with the ’HundredGigE0/0/0/5’ interface. However, it is stated that the interface is operational, indicating it’s not a critical failure. | |
| DeepSeek-R1 | Non-critical | Slight inefficiency due to output data rate increase relative to input with observed packet loss. | ||
| Mistral | Non-critical | The high levels of data rates and load on interface ’HundredGigE0/0/0/5’ are within acceptable bounds for a production network, indicating normal operation. However, it is advised to monitor these values over time to ensure they do not exceed thresholds, indicating potential network congestion or performance degradation. | ||
| Llava:7b | Agent | Critical | An issue with the network interface is causing output drops on the device, which could impact network performance and reliability. | |
| IBM’s Granite3.2:8b | Non-critical | The device’s data rates, packet rates, and reliability metric all indicate normal operation with no unexpected spikes or drops in traffic. Although the load is high at 26.0, it does not signify a fault but heavy utilization, supported by the absence of critical-indicating peak values (peak-input/output-data-rate, peak-input/output-packet-rate). | ||
| Microsoft’s Phi4:14b | Non-critical | The interface operates within expected parameters, with no indicators of bandwidth saturation, significant packet loss, or unreliability. Metrics such as data rate and load are normal, and reliability is at maximum without errors affecting performance. Despite some high values mentioned elsewhere, none relate to a critical fault for this specific instance. |
| Models | Actor | Query | Severity | Cause Summary |
| Llama3.2 | “Predict whether Device with ’name’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters’, ’time’: ’2017-09-01 10:35:19.556000’, ’EncodingPath’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters’, ’Producer’: ’leaf3’, ’bytes-received’: ’934494113183718.0’, ’bytes-sent’: ’2736075649406230.0’, ’carrier-transitions’: ’0.0’, ’crc-errors’: ’0.0’, ’input-drops’: ’0.0’, ’input-errors’: ’0.0’, ’input-ignored-packets’: ’0.0’, ’input-queue-drops’: ’0.0’, ’interface-name’: ’HundredGigE0/0/0/5’, ’output-buffer-failures’: ’0.0’, ’output-drops’: ’19401038.0’, ’output-errors’: ’0.0’, ’output-queue-drops’: ’0.0’, ’packets-received’: ’224932326520.0’, ’packets-sent’: ’1573333104341.0’ has a Critical fault or Non-critical fault.” | Critical | High data rate on the interface combined with high packet loss indicates a potential interface issue. | |
| DeepSeek-R1 | Critical | The high number of output drops (over 19 million) suggests that there may be an issue with data transmission capacity or buffer overflow on the output link interface, potentially indicating hardware exhaustion or configuration errors leading to packet loss. | ||
| Llava:7b | Agent | Critical | The interface has experienced output queue drops, which can result in lost data and reduced network performance. This can have serious implications for the functionality of the network device. | |
| Mistral | “Predict whether Device with ’name’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters’, ’time’: ’2017-09-01 10:17:09.336000’, ’EncodingPath’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters’, ’Producer’: ’leaf3’, ’bytes-received’: ’5344118565224976.0’, ’bytes-sent’: ’5096276026294021.0’, ’carrier-transitions’: ’0.0’, ’crc-errors’: ’390.0’, ’input-drops’: ’0.0’, ’input-errors’: ’390.0’, ’input-ignored-packets’: ’0.0’, ’input-queue-drops’: ’0.0’, ’interface-name’: ’HundredGigE0/0/0/30’, ’output-buffer-failures’: ’0.0’, ’output-drops’: ’2573752423.0’, ’output-errors’: ’0.0’, ’output-queue-drops’: ’0.0’, ’packets-received’: ’1974518315803.0’, ’packets-sent’: ’2244342803311.0’ has a Critical fault or Non-critical fault.” | Critical | Potential network congestion, cable problems or misconfiguration due to high input errors and output drops on the ’HundredGigE0/0/0/30’ interface. Additionally, investigate possible causes for CRC errors across all interfaces. |
| Models | Actor | Query | Severity | Cause Summary |
| IBM’s Granite3.2:8b | “Predict whether Device with ’name’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/data-rate’, ’time’: ’2017-09-01 10:31:39.580000’, ’EncodingPath’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/data-rate’, ’Producer’: ’spine2’, ’bandwidth’: ’100000000.0’, ’input-data-rate’: ’10273100.0’, ’input-load’: ’26.0’, ’input-packet-rate’: ’227678.0’, ’interface-name’: ’HundredGigE0/0/0/17’, ’load-interval’: ’0.0’, ’output-data-rate’: ’12093337.0’, ’output-load’: ’30.0’, ’output-packet-rate’: ’408305.0’, ’peak-input-data-rate’: ’0.0’, ’peak-input-packet-rate’: ’0.0’, ’peak-output-data-rate’: ’0.0’, ’peak-output-packet-rate’: ’0.0’, ’reliability’: ’255.0’ has a Critical fault or Non-critical fault.” | Critical | The high reliability metric (255) indicates a potential interface failure, which can lead to significant network disruptions. Despite no individual metrics indicating critical faults, the overall non-responsive or malfunctioning state of ’HundredGigE0/0/17’ is classified as critical due to its impact on network operations. | |
| Microsoft’s Phi4:14b | Predict whether Device with ’name’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters’, ’time’: ’2017-09-01 10:18:59.451000’, ’EncodingPath’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters’, ’Producer’: ’leaf3’, ’bytes-received’: ’5344118565224976.0’, ’bytes-sent’: ’5096276026294021.0’, ’carrier-transitions’: ’0.0’, ’crc-errors’: ’390.0’, ’input-drops’: ’0.0’, ’input-errors’: ’390.0’, ’input-ignored-packets’: ’0.0’, ’input-queue-drops’: ’0.0’, ’interface-name’: ’HundredGigE0/0/0/30’, ’output-buffer-failures’: ’0.0’, ’output-drops’: ’2573752423.0’, ’output-errors’: ’0.0’, ’output-queue-drops’: ’0.0’, ’packets-received’: ’1974518315803.0’, ’packets-sent’: ’2244342803311.0’ has a Critical fault or Non-critical fault | Critical | There is a possibility that the metrics are being incorrectly scaled or recorded due to misconfiguration or reporting inaccuracies by the telemetry system. |
| Models | Actor | Query | Severity | Cause Summary |
| Llama3.2 | “Predict whether Device with ’name’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters’, ’time’: ’2017-09-01 10:35:46.985999’, ’EncodingPath’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters’, ’Producer’: ’leaf3’, ’bytes-received’: ’659311227161861.0’, ’bytes-sent’: ’388892590647867.0’, ’carrier-transitions’: ’0.0’, ’crc-errors’: ’0.0’, ’input-drops’: ’0.0’, ’input-errors’: ’0.0’, ’input-ignored-packets’: ’0.0’, ’input-queue-drops’: ’0.0’, ’interface-name’: ’HundredGigE0/0/0/8’, ’output-buffer-failures’: ’0.0’, ’output-drops’: ’0.0’, ’output-errors’: ’0.0’, ’output-queue-drops’: ’0.0’, ’packets-received’: ’165436307368.0’, ’packets-sent’: ’112420913236.0’ has a Critical fault or Non-critical fault.” | Critical | No Feedback | |
| DeepSeek-R1 | Predict whether Device with ’name’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters’, ’time’: ’2017-09-01 10:17:40.959000’, ’EncodingPath’: ’Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters’, ’Producer’: ’spine2’, ’bytes-received’: ’765732261758138.0’, ’bytes-sent’: ’692455587027158.0’, ’carrier-transitions’: ’0.0’, ’crc-errors’: ’0.0’, ’input-drops’: ’0.0’, ’input-errors’: ’0.0’, ’input-ignored-packets’: ’0.0’, ’input-queue-drops’: ’0.0’, ’interface-name’: ’HundredGigE0/0/0/14’, ’output-buffer-failures’: ’0.0’, ’output-drops’: ’0.0’, ’output-errors’: ’0.0’, ’output-queue-drops’: ’0.0’, ’packets-received’: ’257183573922.0’, ’packets-sent’: ’295378443912.0’ has a Critical fault or Non-critical fault. | Non-critical | No significant issues observed with the interface operational state or data rates within acceptable limits. | |
| Mistral | Critic | Non-critical | The given query data does not indicate a critical fault in the device’s interface. The high traffic and data rates shown can be seen as heavy load, which is generally considered non-critical, but monitoring for potential issues in the near future is recommended. To mitigate this, network administrators might consider optimizing traffic or upgrading bandwidth accordingly. | |
| Llava:7b | Non-critical | No Feedback | ||
| IBM’s Granite3.2:8b | Non-critical | The provided data does not indicate any critical faults on interface HundredGigE0/0/0/14. All counters such as bytes-received, bytes-sent, carrier-transitions, crc-errors, input-drops, input-errors, input-ignored-packets, input-queue-drops, output-buffer-failures, output-drops, output-errors, and output-queue-drops are either zero or within normal operation ranges. The interface is up and functioning normally according to the given metrics. | ||
| Microsoft’s Phi4:14b | Non-critical | No Feedback |