|
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
|
| Volume 187 - Issue 127 |
| Published: July 2026 |
| Authors: Veera Ravindra Divi |
10.5120/ijcaa68c5de71c8c
|
Veera Ravindra Divi . Context-Aware Multi-Agent Root Cause Analysis for Distributed Transaction Failures. International Journal of Computer Applications. 187, 127 (July 2026), 45-52. DOI=10.5120/ijcaa68c5de71c8c
@article{ 10.5120/ijcaa68c5de71c8c,
author = { Veera Ravindra Divi },
title = { Context-Aware Multi-Agent Root Cause Analysis for Distributed Transaction Failures },
journal = { International Journal of Computer Applications },
year = { 2026 },
volume = { 187 },
number = { 127 },
pages = { 45-52 },
doi = { 10.5120/ijcaa68c5de71c8c },
publisher = { Foundation of Computer Science (FCS), NY, USA }
}
%0 Journal Article
%D 2026
%A Veera Ravindra Divi
%T Context-Aware Multi-Agent Root Cause Analysis for Distributed Transaction Failures%T
%J International Journal of Computer Applications
%V 187
%N 127
%P 45-52
%R 10.5120/ijcaa68c5de71c8c
%I Foundation of Computer Science (FCS), NY, USA
A single distributed transaction can touch a dozen services, several databases, an authorization layer, a message bus, and one or two third-party dependencies before it either commits or fails. When it fails, the engineer on call rarely sees the cause directly. They see a symptom—a 500 returned to a caller, a stalled queue, a customer ticket—and then spend the bulk of their time reconstructing the transaction path, deciding which team owns the failing hop, correlating logs across service boundaries, and separating an upstream cause from an internal bug from a downstream outage. This paper presents CARMA, a Context-Aware Root-cause Multi-Agent Analysis framework that decomposes this work across specialized agents: a ticket-understanding agent, a log-retrieval agent, a dependency-classification agent, a payload-analysis agent, a policy-checking agent, and a remediation-recommendation agent, coordinated by an orchestrator. The framework’s central idea is evidence-weighted aggregation: each agent emits scored, citable evidence rather than a verdict, and the orchestrator resolves a root-cause class from the weighted set, which keeps the final answer grounded in retrieved signals rather than free generation. A synthetic benchmark is defined that injects seven representative failure classes—malformed request, authorization mismatch, cache inconsistency, timeout propagation, dependency unavailability, schema drift, and business-rule rejection—into generated transaction graphs, together with an evaluation protocol spanning classification accuracy, mean-time-to-diagnosis, false escalation rate, remediation precision, human-review workload, latency, and cost. All reported numbers are illustrative figures produced by the simulation harness and are intended to characterize the framework’s behavior, not to report production performance.