Papers for

cloud operations teams

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Slant reduces CPU use and latency in microservice traffic routing

Slant: Shaping Traffic for Resource-Efficient Microservices

Abstract: Microservice architectures rely on load balancers to distribute requests across service replicas, yet existing designs largely optimize for balanced routing without considering how routing shapes autoscaling signals and resource efficiency. We present Slant, a resource-aware load balancing framework that intentionally creates safe traffic imbalance to improve resource utilization. Slant profiles service-specific critical points, computes conservative multi-dimensional capacity, derives imbalance-aware routing weights that maintain hot and cold pods, and falls back to safer behavior under anomalies. By exposing clearer utilization signals, Slant works with existing vertical pod autoscalers (VPAs) without modification. Experiments on three microservice benchmarks show that Slant reduces allocated CPU cores by up to 26\% while lowering P99 latency by up to 18\% compared to Round-Robin. Under dynamic workloads, Slant triggers VPA scale-up 45\% faster and completes scale-in 40\% faster. Under anomalies, it recovers 40\% faster from pod failures and limits latency amplification to 1.8$\times$ versus 2.6$\times$ during downstream slowdowns.

Wed 28 OctDistributed, Parallel, and Cluster Computing
The gist
Microservices use load balancers to split work evenly among servers, but this balanced approach can hide how busy each server really is, making it harder to save resources. The authors created Slant, which deliberately sends uneven traffic to servers to better reveal usage patterns, helping automated tools adjust resources more quickly and efficiently. Slant improves CPU use by up to 26% and reduces delays by up to 18%, and it recovers faster from sudden problems. This method works with existing autoscaling tools without needing changes.
Open → 2610.38778v1

Simple large language models diagnose microservice failures better than complex agents

Free to Look, Free to Reason: Simple LLM Harnesses Outdiagnose Hand-Crafted Root Cause Analysis Agents

Abstract: Root cause analysis (RCA) of microservice failures has attracted many LLM agents whose investigation is hand-crafted, through standard operating procedures, fixed stages and role agents. Each is evaluated on its own data against few baselines, so it is unknown whether this design beats letting a capable model investigate on its own. We compare three simple harnesses that prescribe none of the model's calls (one call over an evidence package, a SQL agent and the Codex coding agent) with five published LLM RCA agents and with statistical and causal methods on RCAtlas, 90 validated cases from eight public datasets, across six models and three reasoning efforts. The simple harnesses are the most accurate (PR@1 65-77% on three mid-tier models), ahead of the published agents (16-53%) and the non-LLM methods (6-39%), on every model on which both families were run. The published agents fix from a tenth to all of their model calls in the program, and a case study shows how these prescriptions skip the decisive evidence. A stronger model mainly improves reliability, a multi-turn harness mainly improves aptitude, and more reasoning effort changes accuracy by a few points at most while multiplying the time by up to seven. Among runs more accurate than the best non-LLM method, every Pareto-optimal run in cost or time uses a simple harness.

Mon 26 OctArtificial IntelligenceDistributed, Parallel, and Cluster ComputingSoftware Engineering
The gist
Figuring out what caused a software failure in complex systems called microservices is hard, so some computer scientists build step-by-step programs to guide AI models in finding the cause. This paper shows that just letting simpler AI models freely investigate the evidence outperforms these complicated, hand-designed processes. The authors tested their approach on many real-world cases and found it was more accurate and often faster. They also discovered that improving the AI model itself helps reliability, while letting it do multiple reasoning steps improves its skill level.
Open → 2610.35767v1

Scheduling diverse job assignments while keeping tasks on time

Diverse Schedules for Makespan Minimization on Unrelated Machines

Abstract: We study makespan minimization on unrelated machines with the additional goal of constructing diverse schedules: Instead of outputting a single schedule, we seek a collection of schedules with provable makespan guarantees and substantially different job assignments. Committing to a single schedule in advance may be undesirable. Processing times may be uncertain, and constraints or domain knowledge may emerge later, so $k$ schedules of similar quality offer meaningful alternatives. We measure pairwise diversity by the weighted Hamming distance between job assignments and study the two standard objectives in the diverse-solutions literature: max-sum diversity, which maximizes the total pairwise distance between schedules, and max-min diversity, which maximizes the smallest pairwise distance. For the max-sum objective, we show that optimal diversity can be achieved in polynomial time without sacrificing the classic makespan approximation factor. For every feasible makespan target $T$, we can compute $k$ schedules of makespan at most $2T$ whose max-sum diversity is optimal among all $k$ schedules of makespan at most $T$. Therefore, we match the classic factor-$2$ makespan guarantee of Lenstra, Shmoys, and Tardos (Math. Prog., 1990) and preserve optimal diversity. For the max-min objective, we show that the diversity problem is inherently harder. Namely, we show that, even without makespan constraints, deciding whether three schedules of given pairwise diversity exist is NP-hard. We complete this with two complementary bicriteria approximation algorithms for every fixed $k$ and $\varepsilon \in (0,1)$. The first preserves almost all of the optimal max-min diversity with makespan at most $(3\lceil12/\varepsilon\rceil+1)T$. The second keeps the makespan arbitrarily close to the classic $2$ guarantee while achieving a $\frac{1}{2}(1-\varepsilon)$ fraction of the optimal max-min diversity.

Tue 20 OctData Structures and Algorithms
The gist
Scheduling jobs on machines where each job takes different times is hard, especially when conditions change. The authors look for not just one plan but multiple different plans that finish jobs around the same time. They show how to find many well-performing schedules that differ greatly from each other, giving options if some conditions change or new rules appear. However, they also prove that finding schedules that are very different in the strictest way is much harder. They provide new methods balancing schedule quality and diversity.
Open → 2610.28514v1

Beacon improves cloud anomaly detection by linking multimodal data

BEACON: Bridging Multimodal Semantics and Asynchronous Propagation for Cloud System Anomaly Detection

Abstract: Modern large-scale cloud systems continuously generate massive and multimodal observability data, such as time-series metrics, log records, and system dependency graphs, which reflect the health state of the system. To ensure reliable cloud system operation, anomaly detection models identify abnormal states by analyzing these multimodal observations. However, existing approaches rely on simple fusion strategies and graph learning, ignoring the semantic gap among modalities and the asynchronous spatio-temporal dependencies across system instances over time. To this end, we propose BEACON, a framework to Bridge multimodal sEmantics and Asynchronous propagation for Cloud system anOmaly detectioN. Specifically, we introduce a Dynamic Interpretable Multimodal Aggregator (DIMA) that leverages an information-bottleneck mechanism to compress information from the semantics and temporal dynamics of metrics, and aligns them with logs in a shared prototype space. Furthermore, we propose an Asynchronous Spatio-Temporal Propagator (ASTP) that captures temporal dependencies with multi-scale temporal attention and models spatial relations with topology-aware aggregation. This enables asynchronous propagation of anomalies across system instances. Extensive experiments on three real-world cloud system datasets demonstrate that \textbf{BEACON} consistently outperforms state-of-the-art baselines in anomaly detection.

Tue 20 OctMachine Learning
The gist
Cloud systems produce many different types of data like performance numbers, logs, and graphs that show how parts of the system connect. Detecting problems by looking at this mixed data is hard because the data types don’t naturally fit together and events happen at different times in different parts of the system. The authors present BEACON, a method that better combines these data types and tracks issues as they spread asynchronously across the system. Their tests on real cloud data showed BEACON finds anomalies more accurately than previous methods.
Open → 2610.27542v1

Measuring lingering access risks in tool-using ai agents

CreepScope: Measuring Post-Use Authorization Exposure in Tool-Using Agents

Abstract: Authorization checks at individual tool calls do not reveal how long earlier authority remains usable. We study this lifecycle failure as privilege creep: a capability stays reachable after its last justified workflow step. We present CreepScope, a trace-oriented evaluation protocol that samples reachable authority at every step and separates no-remaining-use exposure into stale-after-use and never-required components; Capability-Step Exposure (CSE) counts total stepwise overexposure and Residual Privilege Debt (RPD) the terminal residue, while stale-after-use exposure is the direct privilege-creep measure. A 96-cell deterministic replay over 12 controlled storage, communication, and cloud-operation workflows validates these semantics: Static Task Scope and Monotonic On-Demand retain mean CSEs of 26 and 13, whereas an oracle-controlled Step Lease has zero CSE and zero residual debt by construction. All three persistent regimes share the same stale-after-use exposure of 13, so their CSE differences come from scope and grant timing rather than post-use retention; Full Access alone adds 91.33 never-required capability-steps. A separate 24-episode local case then lets Qwen2 7B choose tools in one simulated mail workflow: the injected stale send executes in all nine persistent-policy episodes and in none of the three Step-Lease episodes, while all 24 required action sequences complete. These results establish a reproducible containment case, not cross-workflow or cross-model effectiveness. Core metrics are reconstructed from raw events, and exact gates reject incomplete or duplicated evaluation grids.

Sun 11 OctCryptography and Security
The gist
Sometimes software tools keep permissions longer than needed, creating security risks. The authors study this problem called privilege creep, where access stays usable after it's no longer justified. They create a method called CreepScope that tracks how long permissions remain reachable step-by-step. Their tests show different ways tools manage permissions result in various levels of lingering exposure. This helps understand and measure hidden security risks in automated workflows.
Open → 2610.15988v1

TurboProm speeds up metrics monitoring while cutting cloud costs

TurboProm: Low Cost and High Performance Metrics Observability at Scale

Abstract: Many large enterprise and cloud deployments rely on metrics observability solutions (e.g., Prometheus) to monitor key performance indicators of system health (e.g., CPU, memory, network, app-level statistics). Monitoring and analyzing these metrics presents a significant challenge in terms of cost-latency tradeoffs at scale. Ideally, system operators would like immediately deployable and backwards compatible solutions to improve the cost-latency tradeoffs without significant impact on the fidelity of their observability applications. Unfortunately, existing solutions including state-of-art timeseries databases and custom approximate querying solutions fail on one or more aspects. In this paper, we present the design and implementation of TurboProm, a backwards-compatible drop-in accelerator for metrics observability deployments. TurboProm recasts metrics analytics tasks using a semantic-preserving summary view rather than classical query-centric view. Instead of estimating query results on raw timeseries metrics data, TurboProm uses semantic-preserving summaries that enable high-fidelity analytics with significant cost-latency improvements. We present a practical implementation of TurboProm that can be retrofitted to any existing observability deployment. We evaluate TurboProm on diverse real and synthetic workloads against state-of-art solutions and show that it can provide significant reduction in query latency and cost. TurboProm is open-source at https://github.com/ProjectASAP/ASAPQuery.

Sat 10 OctDatabasesDistributed, Parallel, and Cluster ComputingNetworking and Internet Architecture
The gist
Many big companies use tools like Prometheus to monitor how their computer systems are working by collecting lots of data points. But handling and analyzing this data quickly and cheaply can be hard when there is a lot of it. The authors present TurboProm, a tool that can be added to existing systems without changing them, which summarizes this data in a smart way to keep the details accurate while making queries faster and cheaper. They tested TurboProm with real and simulated data and found it reduces delays and costs significantly compared to current solutions.
Open → 2610.14483v1

Latency aware multitask learning optimizes multi agent workflows

Optimize Once, Execute Fast: Latency-Aware Multi-Agent Workflow Learning for Recurrent Queries

Abstract: Large Language Model-based Multi-Agent Systems (LLM-based MAS) have shown remarkable success in solving complex tasks by coordinating specialized agents through multi-step workflows. To overcome the high cost and specificity of manually designed workflows, recent research has shifted toward learning them automatically. However, a key limitation remains: while agent calls introduce significant latency due to model inference time and service congestion, most automated methods optimize solely for downstream performance, ignoring execution time (makespan). This issue is amplified when workflows are reused across recurring queries, making latency accumulate over time. This limits deployment in recurrent applications such as AI customer support and AI cloud troubleshooting, where users expect fast responses. To bridge this gap, we introduce a new problem, termed latency-aware workflow generation, where the objective is to minimize workflow makespan while aiming to retain downstream performance. We propose LAWA (Latency-Aware Workflow optimizAtion), a novel framework that reduces makespan via theoretically grounded graph edits targeting critical-path bottlenecks. By unifying a graph generator with this graph-editing procedure, LAWA supports both de novo workflow generation and refinement of existing ones. Empirical results across seven benchmarks demonstrate that LAWA significantly reduces makespan while achieving competitive task performance, supporting efficient reuse of multi-agent workflows for recurrent queries.

Sat 10 OctMultiagent Systems
The gist
Multi-agent systems use large language models to solve complex tasks by coordinating various specialized agents. Designing workflows for these systems manually is costly and specific, so researchers want to learn workflows automatically. The paper points out that existing methods ignore the time it takes to run these workflows, which can add up when queries repeat. The authors propose a new method called LAWA that optimizes workflows to reduce total latency while keeping performance strong. This helps make such multi-agent workflows faster and more practical for repeated use.
Open → 2610.14481v1

Dependency-aware method improves learning for terminal command agents

Credit Where It Matters: Dependency-Aware Policy Optimization for Terminal Agents

Abstract: Terminal-using agents benefit from reinforcement learning (RL) in coding, debugging, and other multi-step terminal tasks. In these tasks, later commands often depend on information or intermediate results produced by earlier commands. However, existing trajectory-level and step-level credit assignment methods do not explicitly trace the read-write dependencies through which commands affect the final outcome. Consequently, training signals could still be assigned to irrelevant operations, weakening learning from relevant steps. In this paper, we propose Dependency-Aware Group Policy Optimization (DepGPO), which uses execution dependencies between commands to guide credit assignment for terminal agents. Specifically, we construct a command dependency graph from execution traces and trace backward from the resources inspected by the task verifier. We then assign credit to relevant writes and their supporting reads along these paths, and use it to redistribute trajectory advantages across steps. Extensive comparative experiments and ablation studies demonstrate that DepGPO improves task performance and training stability on complex terminal tasks.

Fri 2 OctArtificial Intelligence
The gist
When computer programs learn to complete tasks step by step, some steps depend on what happened before. The authors found that current learning methods don’t always figure out which earlier steps actually matter for success. They created a new technique that tracks how commands depend on each other and uses this to better give credit to important steps. This helps the learning program get better at complex tasks and makes training more stable.
Open → 2610.03634v1

Verifier model clarifies when execution evidence is complete or missing

Evidence Coverage for Intent-Bound Execution: Scope, Obligations, and Cutoff Reasoning

Abstract: A verifier may authenticate every available record and still lack grounds to call an execution account complete. Such a claim requires a justified account of which records were due for the execution being assessed. We present an analytical model for retrospective coverage of declared execution-evidence obligations. Its scope binds a structured Intent, an exact Candidate, a selected analytical attempt, an execution and evidence boundary, a stage horizon, a fixed record-obligation profile, a named verifier, and an assessment cutoff. Branch and trigger premises determine obligation instances; source competence, content, integrity, and object and stage bindings determine admissibility. We distinguish closure of the obligation inventory from closure of the relevant verifier view, and define three reporting results: COMPLETE_WITHIN_SCOPE, INCOMPLETE, and UNKNOWN. These results concern current coverage of obligations due at the cutoff. Execution progress, external outcome knowledge, and historical delivery timeliness are reported separately. Constructed service-principal-disablement cases demonstrate complete dispatch and refusal branches, a due but missing final-result record, subsequent coverage after late delivery, and the limits of extending one selected attempt's coverage to all attempts. The contribution is an execution-specific composition of scope, branch, horizon, obligations, admissibility, view, and cutoff. Completeness remains conditional on the declared profile and assessment premises.

Thu 1 OctCryptography and Security
The gist
Sometimes, checking all available records about how a task was done doesn’t prove that the story is complete. The authors created a clear way to decide if all the needed evidence for a task is there, based on rules about what evidence was supposed to show up and when. They also show how to handle late evidence or missing pieces, and how to report if the evidence is complete, incomplete, or unknown at a certain point in time. This helps people understand and trust that what they see about task results really covers what should be known.
Open → 2610.01386v1

Predicting inference cost speeds up diffusion large language model serving

Denoising Surface: Modeling and Predicting Inference Cost for Diffusion LLM Serving

Abstract: As diffusion large language models (dLLMs) become more capable, they are moving from research settings to real-world \textit{serving}, where request management (such as scheduling and resource allocation) relies on accurate estimation of per-request inference cost. However, common cost proxies fall short for dLLMs: output length ignores that one forward pass can unmask multiple tokens, and denoising-step count ignores the \textit{heterogeneous} per-step costs. We observe that the block-autoregressive generation mechanism induces a two-dimensional execution structure over output blocks and within-block denoising steps, whereas these proxies collapse it into a scalar, discarding information essential for characterizing the cost. Motivated by this insight, we propose the Denoising Workload Surface (DWS), which preserves this two-dimensional block-step structure as a probability surface to weight the heterogeneous per-step costs. We then design a coarse-to-fine training scheme that enables a lightweight prompt-only predictor to accurately predict the complex DWS. This predictor runs efficiently even on a single CPU core, avoiding GPU contention with the serving model. Since DWS decouples request-dependent execution behavior from deployment-specific cost factors, the predictor transfers across hardware configurations without retraining. In \textit{real-world} serving experiments, DWS reduces cost-prediction error by up to $2.50\times$ over scalar-based predictors, while the DWS-guided shortest-job-first scheduler reduces end-to-end latency by up to $1.92\times$ for online chatbots.

Wed 30 SeptMachine Learning
The gist
Diffusion large language models (dLLMs) are powerful but estimating how long they take to respond is tricky because their work happens in steps and blocks. The authors saw that common ways to guess the cost are too simple and miss important details. They invented a method called the Denoising Workload Surface (DWS) that captures this two-dimensional step-block pattern to predict inference cost more accurately. Their predictor runs fast on CPUs and adapts across different hardware setups. Using DWS improves cost predictions and reduces delays in real chatbot services.
Open → 2610.00499v1

AI software factory speeds data system coding and operations by three times

Towards an AI Software Factory for Data Systems

Abstract: AI-assisted coding tools deliver significant acceleration of coding, but only limited impact across the end-to-end software development lifecycle (SDLC)--an Amdahl's law effect! In this paper, we discuss our progress towards building an AI SW Factory that accelerates all the stages of SDLC-Targeting, Coding, Reviewing, and Ops. The AI SW Factory produces a metadata exhaust that enables self-improvement by fine-tuning model weights and updating our World Model (a rich data substrate). We focus on Data Systems and the important class of Evolutionary Coding Tasks (i.e., those with a measurable objective to hill-climb) and report on 1) scaled deployments at Microsoft (tens of repositories) leading to 3x engineering efficiency above agentic coding and up to 22x token efficiency, and 2) several open challenges.

Mon 28 SeptArtificial IntelligenceDatabasesSoftware Engineering
The gist
Writing software involves many steps beyond just coding, and improving only one step only helps so much. The authors built an AI-powered software factory that speeds up all parts of the software life cycle, including planning, coding, reviewing, and operations. This system learns from ongoing work to continuously improve itself. They tested it in many Microsoft projects focused on data systems and found it made engineers work three times faster and handled code more efficiently. Some challenges remain for wider adoption.
Open → 2609.36323v1

Confidence guided method improves anomaly detection in microservice systems

Confidence-Guided Cross-Modal Knowledge Transfer for Multimodal Anomaly Detection in Microservice Systems

Abstract: Accurate anomaly detection is essential for reliable and secure operations of microservice systems. While an increasing number of studies have shifted from unimodal modeling to multimodal interaction and fusion, effectively leveraging reliable cross-modal information remains challenging. The challenge primarily stems from two aspects. Firstly, different modalities are influenced by factors like load fluctuations, leading to dynamically changing reliability. Secondly, multimodal data exhibit heterogeneity in both structure and semantics. Therefore, we propose a confidence-guided Cross-Modal knowledge Transfer method for multimodal Anomaly Detection (CMT-AD). It jointly models metrics and logs within a unified deep clustering framework and estimates modality reliability through the soft clustering distributions, where clustering uncertainty is quantified into confidence scores. Guided by these confidence scores, the model actively analyzes the contributions of each modality in cross-modal interactions and supplements low-confidence modalities with knowledge from high-confidence ones. To further mitigate cross-modal heterogeneity, we introduce a gated intermediate modality and design structural and semantic consistency constraints that align the original modalities with the intermediate modality to preserve similarity structures and semantic distributions across modalities. Furthermore, intra-modal and cross-modal regularization terms are incorporated to enhance cluster compactness and mitigate negative transfer. We evaluated CMT-AD on three large-scale datasets, and the results demonstrate that CMT-AD outperforms state-of-the-art approaches and achieves an F1-score higher than 0.9.

Tue 22 SeptSoftware Engineering
The gist
Detecting problems in complex microservice systems is hard because data comes from different sources that can vary in reliability and meaning. The authors propose a method that measures how trustworthy each data source is and uses the reliable ones to help less reliable sources. They combine logs and performance metrics in a deep learning model that groups similar behaviors, improving problem detection. Their tests show better results than existing methods on several large datasets.
Open → 2609.25856v1

Maple supports ongoing optimization with language and memory

MAPLE: Memory-Augmented Planning with Language and Evolution

Abstract: Domain practitioners understand their business constraints but may lack operations-research expertise or dedicated support. LLM-based optimization agents translate natural-language requirements into models or solver programs that established optimization tools can execute. This progress makes optimization more accessible, but real-world operations are dynamic: changing demand, resources, and priorities require updates to data, constraints, and objectives. Methods centered on isolated requests offer limited support for rapid adaptation that preserves earlier decisions and reuses useful search results. We introduce MAPLE (Memory-Augmented Planning with Language and Evolution), an agent for maintaining optimization problems through successive natural-language requests. MAPLE combines language-based problem construction with mathematical programming and evolutionary search. It retains the optimization program, accepted plans, earlier updates, and candidate solutions for subsequent requests. We introduce NLDO, a benchmark of 15 trajectories and 180 updates spanning selection, scheduling, rostering, routing, and cloud-resource placement. In the main evaluation, MAPLE completes all trajectories and achieves online scalar quality of 0.951 and a Pareto hypervolume ratio of 0.875. Controlled comparisons further show that maintaining executable state improves update validity and can preserve useful search information across substantial revisions.

Thu 10 SeptArtificial Intelligence
The gist
Optimization problems in real life often change over time, requiring updates while keeping past good decisions. The authors present MAPLE, a system that uses natural language requests combined with mathematical and evolutionary methods to update and maintain optimization solutions. MAPLE remembers earlier plans and candidate solutions to help quickly adapt to changes. Their tests show MAPLE effectively handles sequences of updates in diverse optimization tasks like scheduling and routing.
Open → 2609.11636v1

AI safely fixes backend failures using sandbox and risk checks

Can AI Remediate Backend Failures Safely? GuardedAct with Blast-Radius-Aware Sandboxing

Abstract: Large Language Models (LLMs) have shown promising capabilities in generating remediation actions for microservice failures. However, directly executing AI-generated repair actions in production risks cascading collateral damage. We propose GuardedAct, a sandbox-first remediation framework that interposes a blast-radius-aware verification layer between the LLM action generator and the production environment. GuardedAct operates in four phases: (1) ingesting a diagnosis report together with the live system topology and recent telemetry, (2) prompting an LLM to produce a ranked list of candidate remediation actions, (3) simulating each action in a lightweight digital-twin sandbox that estimates the blast radius and assigns a risk label, and (4) enforcing a rollback-confidence gate that auto-executes only low-risk actions while escalating high-risk ones for human review. We evaluate GuardedAct on five fault scenarios injected into the DeathStarBench social-network application. Experimental results show that GuardedAct achieves an overall recovery rate of 87.4% while reducing collateral damage by 79.7% relative to direct LLM execution (from 25.6% to 5.2%), at the cost of a modest sandbox-induced increase in mean time to recovery (approximately 8 s). Ablation studies confirm that each component contributes meaningfully to the safety-speed trade-off.

Thu 10 SeptDistributed, Parallel, and Cluster ComputingSoftware Engineering
The gist
Fixing backend computer problems automatically with AI risks causing more trouble if done directly. The authors introduce GuardedAct, a system that tests AI-recommended fixes in a safe copy of the system to estimate their risk before applying them. Low-risk fixes are applied immediately, while risky ones go for human review. Tests show this approach fixes most problems while greatly reducing collateral damage, with only a small delay added.
Open → 2609.11264v1