# Monitoring

Monitoring is a DevOps discipline that collects production feedback and application performance and usage data through telemetry to detect, diagnose, and mitigate issues.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## 4 GB of Logs a Minute: A Kafka Monitoring Incident With 20 Minutes to Spare

DevFeed: [4 GB of Logs a Minute: A Kafka Monitoring Incident With 20 Minutes to Spare](<https://devfeed.tech/articles/4-gb-of-logs-a-minute-a-kafka-monitoring-incident-with-20-minutes-to-spare-146459.md>)

Original publisher: [Read original article](<https://linuxhandbook.com/blog/kafka-monitoring-incident/>)

Author: Yash Kiran Patil

Published: 2026-11-20T09:34:13Z

Content type: tutorial

Language: en

Sources: [Linux Handbook](<https://devfeed.tech/sources/linux-handbook.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [incident management](<https://devfeed.tech/topics/incident-management.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Logging and metrics](<https://devfeed.tech/topics/logging-and-metrics.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [availability](<https://devfeed.tech/tags/availability.md>), [blog](<https://devfeed.tech/tags/blog.md>), [bounded](<https://devfeed.tech/tags/bounded.md>), [broker](<https://devfeed.tech/tags/broker.md>), [bug](<https://devfeed.tech/tags/bug.md>), [canary](<https://devfeed.tech/tags/canary.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [cause](<https://devfeed.tech/tags/cause.md>), [change](<https://devfeed.tech/tags/change.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [contain](<https://devfeed.tech/tags/contain.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [incident](<https://devfeed.tech/tags/incident.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [logs](<https://devfeed.tech/tags/logs.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [time](<https://devfeed.tech/tags/time.md>), [warnings](<https://devfeed.tech/tags/warnings.md>)

### AI overview

A partial JMX Exporter upgrade left Kafka brokers on versions 1.6.0 and 0.9.0; under the new scrape configuration, older agents emitted rapidly growing Jetty warnings, putting disk capacity at risk before traffic began. The account links the warnings to the mixed rollout but says their precise cause is unproven without request paths, responses, configuration, and stack traces. Operators used a supervised loop to truncate one verified active log and buy time, preserving a warning sample first; this destructive workaround does not fix exporter behavior or reclaim space from deleted-but-open files. The durable response was to standardize agent versions and restart brokers one at a time during a maintenance window, checking cluster health and exporter and Prometheus metrics after each restart. The article recommends bounded log retention, version inventory, canary checks, and measured tuning rather than assuming an endpoint or concurrency bug.

### Source excerpt

A mixed JMX Exporter fleet, rapidly growing Jetty warnings, and the difference between buying time and fixing the cause.

## Industrial monitoring startup BrightAI closes $97M investment

DevFeed: [Industrial monitoring startup BrightAI closes $97M investment](<https://devfeed.tech/articles/industrial-monitoring-startup-brightai-closes-97m-investment-144671.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/19/industrial-monitoring-startup-brightai-closes-97m-investment/>)

Author: Maria Deutscher

Published: 2026-11-20T01:37:24Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [brightai](<https://devfeed.tech/tags/brightai.md>), [funding-round](<https://devfeed.tech/tags/funding-round.md>), [industrial](<https://devfeed.tech/tags/industrial.md>), [industrial-monitoring](<https://devfeed.tech/tags/industrial-monitoring.md>), [infra](<https://devfeed.tech/tags/infra.md>), [investment](<https://devfeed.tech/tags/investment.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [news](<https://devfeed.tech/tags/news.md>), [sensor](<https://devfeed.tech/tags/sensor.md>), [startup](<https://devfeed.tech/tags/startup.md>), [stateful-sticker](<https://devfeed.tech/tags/stateful-sticker.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>)

### AI overview

BrightAI raised $97 million in a Series A led by Smith Point Capital, with GE Vernova and other venture firms participating. Its State Stickers monitor equipment motion, noise, and vibration; measurements go to a Stateful AI Hub, where AI models look for deviations that may signal failure. The company says accuracy improves as more sensors are deployed at a site. Its software can also analyze drone footage, read asset meters, and use infrared cameras to identify damage or overheating. A Stateful Wearable gives technicians troubleshooting advice, checks safety practices, and turns maintenance data into reports. BrightAI says its products monitor hundreds of thousands of assets across 50,000 sites; GE Vernova plans to expand its use, and BrightAI will use the funding to grow internationally.

### Source excerpt

BrightAI Inc., a startup that helps industrial companies detect malfunctioning equipment, has raised $97 million in funding. Smith Point Capital led the Series A round. BrightAI said in its Wednesday announcement of the deal that a number of other venture capital firms contributed as well. They were joined by GE Vernova Inc., an energy equipment [...] The post Industrial monitoring startup BrightAI closes $97M investment appeared first on SiliconANGLE.

## Resolve AI's SRE-1 model finds root causes of production alerts as AI agents go on call

DevFeed: [Resolve AI's SRE-1 model finds root causes of production alerts as AI agents go on call](<https://devfeed.tech/articles/resolve-ai-s-sre-1-model-finds-root-causes-of-production-alerts-as-ai-agents-go-on-call-144569.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/19/resolve-ais-sre-1-model-finds-root-causes-of-production-alerts-as-ai-agents-go-on-call/>)

Author: Duncan Riley

Published: 2026-11-19T23:11:44Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [site-reliability-engineering](<https://devfeed.tech/topics/site-reliability-engineering.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [post-training](<https://devfeed.tech/topics/post-training.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [incident](<https://devfeed.tech/topics/incident.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [bhupesh-patel](<https://devfeed.tech/tags/bhupesh-patel.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [coinbase](<https://devfeed.tech/tags/coinbase.md>), [cortex-training](<https://devfeed.tech/tags/cortex-training.md>), [crm-analytics](<https://devfeed.tech/tags/crm-analytics.md>), [doordash](<https://devfeed.tech/tags/doordash.md>), [dst-global](<https://devfeed.tech/tags/dst-global.md>), [figma](<https://devfeed.tech/tags/figma.md>), [frontier-model](<https://devfeed.tech/tags/frontier-model.md>), [graphics-processing-units](<https://devfeed.tech/tags/graphics-processing-units.md>), [incident-remediation](<https://devfeed.tech/tags/incident-remediation.md>), [mean-time-to-resolution](<https://devfeed.tech/tags/mean-time-to-resolution.md>), [msci](<https://devfeed.tech/tags/msci.md>), [nasdaq](<https://devfeed.tech/tags/nasdaq.md>), [news](<https://devfeed.tech/tags/news.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [open-weights](<https://devfeed.tech/tags/open-weights.md>), [primary-on-call](<https://devfeed.tech/tags/primary-on-call.md>), [production](<https://devfeed.tech/tags/production.md>), [production-alerts](<https://devfeed.tech/tags/production-alerts.md>), [reinforcement-learning](<https://devfeed.tech/tags/reinforcement-learning.md>), [resolve-ai](<https://devfeed.tech/tags/resolve-ai.md>), [root-cause](<https://devfeed.tech/tags/root-cause.md>), [salesforce](<https://devfeed.tech/tags/salesforce.md>), [salesforce-ventures](<https://devfeed.tech/tags/salesforce-ventures.md>), [sap](<https://devfeed.tech/tags/sap.md>), [series-a](<https://devfeed.tech/tags/series-a.md>), [shadow-mode](<https://devfeed.tech/tags/shadow-mode.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [spiros-xanthos](<https://devfeed.tech/tags/spiros-xanthos.md>), [sre-1](<https://devfeed.tech/tags/sre-1.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>)

### AI overview

Resolve AI has launched Primary On-call, which puts AI agents ahead of human engineers to investigate production alerts and, where team policies allow, close or mitigate them; otherwise it escalates to a person. The agent checks fixes against production baselines until recovery holds, links related investigations, and offers a shadow mode that records the call it would make. Resolve AI says up to 80% of paged alerts are handled without escalation. Its SRE-1 model is a 27-billion-parameter open-weight model, trained with reinforcement learning on private incident data. In the company's tests, a single-investigation pass rate rose from 6.9% to 38.8%; an ensemble matched the strongest frontier model tested on 49 difficult cases at lower cost, and the full system solved about twice as many incidents as general-purpose coding agents across 178 investigations. Primary On-call is generally available; SRE-1 access is limited to Resolve AI's platform. Reported performance figures are company claims.

### Source excerpt

Incident remediation company Resolve AI Inc. has announced the launch of SRE-1, a new model that has been trained to find the root cause of production alerts, and Primary On-call, a new service that puts its artificial intelligence agents on call ahead of human engineers. The new model reflects the company's argument that while AI [...] The post Resolve AI's SRE-1 model finds root causes of production alerts as AI agents go on call appeared first on SiliconANGLE.

## Monitor the efficiency and availability of accelerated computing instances with Amazon EC2 Detailed Monitoring and performance status checks

DevFeed: [Monitor the efficiency and availability of accelerated computing instances with Amazon EC2 Detailed Monitoring and performance status checks](<https://devfeed.tech/articles/monitor-the-efficiency-and-availability-of-accelerated-computing-instances-with-amazon-ec2-detailed-monitoring-and-performance-status-checks-144756.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/monitor-the-efficiency-and-availability-of-accelerated-computing-instances-with-amazon-ec2-detailed-monitoring-and-performance-status-checks/>)

Author: Caroline Frost

Published: 2026-11-19T18:34:57Z

Content type: article

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [gpu monitoring](<https://devfeed.tech/topics/gpu-monitoring.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Monitoring & Alerting](<https://devfeed.tech/topics/monitoring-alerting.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [accelerated](<https://devfeed.tech/tags/accelerated.md>), [accelerated-computing](<https://devfeed.tech/tags/accelerated-computing.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [availability](<https://devfeed.tech/tags/availability.md>), [computing](<https://devfeed.tech/tags/computing.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [one](<https://devfeed.tech/tags/one.md>), [performance](<https://devfeed.tech/tags/performance.md>), [reports](<https://devfeed.tech/tags/reports.md>), [status](<https://devfeed.tech/tags/status.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Amazon EC2 Detailed Monitoring provides one-minute GPU metrics to CloudWatch without an in-guest agent or instance compute, while performance status checks flag recoverable hardware conditions that can impair GPU performance. Metrics include GPU and streaming multiprocessor utilization, memory use, temperature, and interconnect traffic, reported at instance and per-GPU levels; teams can use them to assess capacity and tune workloads. Performance checks appear in the console, `DescribeInstanceStatus`, and CloudWatch, with reboot recommended for a pending GPU memory row remap. Teams can alarm on `StatusCheckFailed_Performance`, then checkpoint work, drain and reboot an affected node, or reset the GPU after stopping its processes. Metrics are limited to supported NVIDIA GPU instance types, carry standard CloudWatch pricing, and complement in-guest tools that provide process, container, pod, and sub-minute detail.

### Source excerpt

Amazon EC2 now reports one-minute per-GPU metrics through Detailed Monitoring and surfaces recoverable hardware conditions with a new performance status check, giving infrastructure teams agentless visibility into accelerated computing efficiency and availability across their fleet.

## The ultimate guide to analyzing and troubleshooting critical issues on Red Hat Enterprise Linux 8 and 9

DevFeed: [The ultimate guide to analyzing and troubleshooting critical issues on Red Hat Enterprise Linux 8 and 9](<https://devfeed.tech/articles/the-ultimate-guide-to-analyzing-and-troubleshooting-critical-issues-on-red-hat-enterprise-linux-8-and-9-144332.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/19/ultimate-guide-to-troubleshooting-critical-issues-on-rhel-8-and-9>)

Author: Kailash Nailwal

Published: 2026-11-19T14:16:41Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [rhel](<https://devfeed.tech/topics/rhel.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [SELinux](<https://devfeed.tech/topics/selinux.md>)

Tags: [blink](<https://devfeed.tech/tags/blink.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [business-operations](<https://devfeed.tech/tags/business-operations.md>), [core](<https://devfeed.tech/tags/core.md>), [critical](<https://devfeed.tech/tags/critical.md>), [devops](<https://devfeed.tech/tags/devops.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-linux](<https://devfeed.tech/tags/enterprise-linux.md>), [environment](<https://devfeed.tech/tags/environment.md>), [guide](<https://devfeed.tech/tags/guide.md>), [hat](<https://devfeed.tech/tags/hat.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [observability](<https://devfeed.tech/tags/observability.md>), [red](<https://devfeed.tech/tags/red.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [red-hat-enterprise](<https://devfeed.tech/tags/red-hat-enterprise.md>), [red-hat-enterprise-linux](<https://devfeed.tech/tags/red-hat-enterprise-linux.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>)

### AI overview

The guide recommends disciplined, evidence-preserving triage for critical RHEL 8 and 9 outages: establish host identity and incident timing, then check CPU, memory, storage, services, networking, logs, security controls, time, resource limits, package history, and hardware for correlated symptoms. It gives commands and observables for each area, with cautions such as distinguishing load from CPU use, static swap from active paging, and ping reachability from application-port availability; it also warns against blind filesystem repairs or globally disabling SELinux. For crashes, it covers `kdump` and `coredumpctl`; for support, it recommends an incident-time `sosreport`, chronological context, logs, and relevant core dumps or SAR data. The text notes that enterprise deployments may need tailored procedures.

### Source excerpt

When a critical outage hits a production environment, time is your most crucial resource. Systems going down, unresponsive microservices, kernel panics, or sudden I/O bottlenecks can quickly jeopardize core business operations. For systems administrators, site reliability engineers (SRE), and DevOps teams managing enterprise workloads on Red Hat Enterprise Linux 8 or 9 (RHEL), having a disciplined and reproducible standard operating procedure (SOP) is what separates a blink from a catastrophe. The post The ultimate guide to analyzing and troubleshooting critical issues on Red Hat Enterprise Linux 8 and 9 appeared first on Red Hat Developer.

## How OpenAI's Performance Factory keeps ChatGPT fast

DevFeed: [How OpenAI's Performance Factory keeps ChatGPT fast](<https://devfeed.tech/articles/how-openai-s-performance-factory-keeps-chatgpt-fast-145835.md>)

Original publisher: [Read original article](<https://openai.com/index/how-openai-performance-factory-keeps-chatgpt-fast>)

Published: 2026-11-19T08:00:00Z

Content type: article

Language: en

Sources: [OpenAI News](<https://devfeed.tech/sources/openai-news.md>)

Topics: [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [codex](<https://devfeed.tech/topics/codex.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [ChatGPT](<https://devfeed.tech/topics/chatgpt.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [codex](<https://devfeed.tech/tags/codex.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [factory](<https://devfeed.tech/tags/factory.md>), [fast](<https://devfeed.tech/tags/fast.md>), [openai](<https://devfeed.tech/tags/openai.md>), [performance](<https://devfeed.tech/tags/performance.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

OpenAI's Performance Factory automates performance regression work from alert to post-deployment verification, while keeping engineers involved in reviewing and merging fixes. A cloud dispatch system assigns Codex agents to tasks that preserve findings across steps and can resume after events such as code review or deployment. Agents use the `perf-forensics` skill and production telemetry to locate when slowdowns began, identify affected requests, examine changes, and propose fixes. Separate Codex reviews challenge diagnoses and fixes; engineers make decisions that require service context or tradeoff judgment. In a manual review of 100 root-cause suggestions, 70% were accurate, while 30% needed refinement or did not fully establish causality. In just over three months, the workflow tracked more than 1,700 investigations and root-caused over 600 cases. OpenAI also backtests investigations and task summaries, monitors agent tool failures, and is exploring proactive detection and agent-implemented low-risk fixes.

### Source excerpt

Learn how OpenAI built the Performance Factory, a system of Codex-powered workflows that finds and fixes performance issues to help keep ChatGPT fast.

## Monitoring Machine Learning Systems in Production: A Multivocal Literature Review

DevFeed: [Monitoring Machine Learning Systems in Production: A Multivocal Literature Review](<https://devfeed.tech/articles/monitoring-machine-learning-systems-in-production-a-multivocal-literature-review-142158.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23293>)

Author: Hira Naveed, Aleksandar Pasquini, Scott Barnett, Chetan Arora, John Grundy, Hourieh Khalajzadeh, Omar Haggag

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [cs-se](<https://devfeed.tech/tags/cs-se.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [inference](<https://devfeed.tech/tags/inference.md>), [literature](<https://devfeed.tech/tags/literature.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [production](<https://devfeed.tech/tags/production.md>)

### AI overview

The review of 94 academic and gray-literature sources finds that production ML monitoring is uneven: tools broadly automate observing system behavior, detecting problems, and communicating findings, while configuration, investigation, and response still rely substantially on people. Monitoring focuses on inference, and no reviewed source covers the whole production system, limiting end-to-end diagnosis. Of 78 sources describing an approach or tool, 45 report no formal evaluation, 24 report offline or controlled evaluations, and nine evaluate live production. Evidence for generative AI monitoring is especially limited and relies heavily on gray literature and vendor claims. The authors propose research directions spanning monitor design, cross-layer diagnosis, proxy validation, corrective responses, production-oriented evaluation, and organizational practices.

### Source excerpt

arXiv:2611.23293v1 Announce Type: new Abstract: Monitoring is essential for maintaining reliable machine learning (ML) systems after deployment. However, knowledge about its practical implementation and effectiveness remains fragmented across academic and gray literature. We present a multivocal literature review of 94 sources (37 academic and 57 gray) covering both traditional ML and generative AI systems. We develop taxonomies covering monitored objects and properties, techniques, input signals, tools, automation, frequency, evaluation, and challenges. Our findings reveal an imbalanced monitoring process. Existing approaches provide broad and largely automated support for observing system behavior, detecting problems, and communicating findings, while monitor configuration, investigation, and response retain substantial human involvement. Monitoring is concentrated on inference, with no source covering the entire production ML system, limiting end-to-end diagnosis. Evidence of effectiveness is also limited: among 78 sources presenting an approach or tool, 45 provide no formal evaluation, 24 report offline or controlled evaluations, and only nine evaluate monitoring in live production. This gap is particularly evident for generative AI, where evidence is dominated by gray literature and vendor claims. We propose six directions for improving monitor design, cross-layer diagnosis, proxy validation, corrective responses, production-oriented evaluation, and organizational practices. Our review provides a structured basis for improving the detection, diagnosis, and resolution of production ML problems.

## Catch production failures early with LangSmith Alerts

DevFeed: [Catch production failures early with LangSmith Alerts](<https://devfeed.tech/articles/catch-production-failures-early-with-langsmith-alerts-142926.md>)

Original publisher: [Read original article](<https://www.langchain.com/blog/langsmith-alerts>)

Author: LangChain Accounts

Published: 2026-11-18T19:33:12Z

Content type: release

Language: en

Sources: [LangChain Blog](<https://devfeed.tech/sources/langchain-blog.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Prometheus alert rules](<https://devfeed.tech/topics/prometheus-alert-rules.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic-apps](<https://devfeed.tech/tags/agentic-apps.md>), [agents](<https://devfeed.tech/tags/agents.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [applications](<https://devfeed.tech/tags/applications.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [docs](<https://devfeed.tech/tags/docs.md>), [error](<https://devfeed.tech/tags/error.md>), [failures](<https://devfeed.tech/tags/failures.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [langsmith](<https://devfeed.tech/tags/langsmith.md>), [latency](<https://devfeed.tech/tags/latency.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [production](<https://devfeed.tech/tags/production.md>), [real-time](<https://devfeed.tech/tags/real-time.md>)

### AI overview

LangSmith Alerts can notify teams about production LLM application issues using error count or rate, average latency, and average feedback score. Alerts can be narrowed with filters such as model, tool call, or run type, then tuned with 5- or 15-minute aggregation windows and thresholds. Notifications can go through PagerDuty or a custom webhook, such as one connected to Slack. The article frames alerts as a way to catch dependency outages, rate limits, latency increases, and output-quality regressions; setup requires production traces already being sent to LangSmith. Run-count and token-usage alerts, relative-change alerts, and custom time windows are listed as future additions.

### Source excerpt

Set up real-time notifications on error rates, run latency & feedback scores to spot failures before your customers do.

## What Is LLM Monitoring? What to Track Once Your Model Is Live

DevFeed: [What Is LLM Monitoring? What to Track Once Your Model Is Live](<https://devfeed.tech/articles/what-is-llm-monitoring-what-to-track-once-your-model-is-live-141933.md>)

Original publisher: [Read original article](<https://montecarlo.ai/blog-llm-monitoring>)

Author: Ruslan Sultanov

Published: 2026-11-18T18:07:29Z

Content type: article

Language: en

Sources: [Monte Carlo](<https://devfeed.tech/sources/monte-carlo.md>)

Topics: [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [ai observability](<https://devfeed.tech/topics/ai-observability.md>), [Monitoring & Alerting](<https://devfeed.tech/topics/monitoring-alerting.md>), [data observability](<https://devfeed.tech/topics/data-observability.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [agent-trust](<https://devfeed.tech/tags/agent-trust.md>), [agent-trust-glossary](<https://devfeed.tech/tags/agent-trust-glossary.md>), [glossary](<https://devfeed.tech/tags/glossary.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-monitoring](<https://devfeed.tech/tags/llm-monitoring.md>), [llm-monitoring-metrics](<https://devfeed.tech/tags/llm-monitoring-metrics.md>), [llm-monitoring-vs-observability](<https://devfeed.tech/tags/llm-monitoring-vs-observability.md>), [llm-performance-monitoring](<https://devfeed.tech/tags/llm-performance-monitoring.md>), [llm-quality-monitoring](<https://devfeed.tech/tags/llm-quality-monitoring.md>), [model](<https://devfeed.tech/tags/model.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [monitoring-llms-in-production](<https://devfeed.tech/tags/monitoring-llms-in-production.md>), [what-is-llm-monitoring](<https://devfeed.tech/tags/what-is-llm-monitoring.md>)

### AI overview

LLM monitoring catches production failures that uptime, latency, and error dashboards miss: an app can be fast and available while returning incorrect or unsafe answers. It continuously tracks performance (latency, tokens, cost, errors), context (source freshness and retrieval), behavior (tool calls, retries, refusals), and output quality (groundedness, relevance, correctness, safety, and user feedback). A practical setup traces requests across retrieval, model, and tool calls; scores traffic with deterministic checks and LLM-as-judge evaluations; alerts on trends or anomalies; then uses trace context to investigate causes such as stale data, prompt changes, or model updates. Evals assess fixed examples before release, monitoring detects production changes, and observability supplies traces and lineage to explain them. The article recommends versioning traces, establishing baselines, checking judges against human review, and assigning alert owners.

### Source excerpt

Your LLM app has been live for a month. Latency is under a second, the error rate is zero, and uptime is perfect. Meanwhile, a product manager forwards a screenshot: the bot told a customer about a discount that ended in March. Nothing on the dashboard moved. That's the gap LLM monitoring fills. This guide ...

## Continuous evaluation of production AI agents on Microsoft Foundry

DevFeed: [Continuous evaluation of production AI agents on Microsoft Foundry](<https://devfeed.tech/articles/continuous-evaluation-of-production-ai-agents-on-microsoft-foundry-141053.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/continuous-evaluation-on-microsoft-foundry/>)

Author: Lyzr Team

Published: 2026-11-18T08:48:33Z

Content type: article

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Trustworthy AI](<https://devfeed.tech/topics/trustworthy-ai.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>), [blue green and canary deployments](<https://devfeed.tech/topics/blue-green-and-canary-deployments.md>), [Dataset development](<https://devfeed.tech/topics/dataset-development.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [backend](<https://devfeed.tech/tags/backend.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [desk](<https://devfeed.tech/tags/desk.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [foundry](<https://devfeed.tech/tags/foundry.md>), [it](<https://devfeed.tech/tags/it.md>), [launch](<https://devfeed.tech/tags/launch.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-foundry](<https://devfeed.tech/tags/microsoft-foundry.md>), [production](<https://devfeed.tech/tags/production.md>), [production-ai](<https://devfeed.tech/tags/production-ai.md>), [service-desk](<https://devfeed.tech/tags/service-desk.md>), [ticketing](<https://devfeed.tech/tags/ticketing.md>)

### AI overview

Microsoft Foundry continuously evaluates sampled production agent responses after they complete, using traces sent to the project's Application Insights. Setup requires connecting Application Insights, configuring evaluators and a RESPONSE_COMPLETED rule, and assigning the project's managed identity the Foundry User role. Results appear in Monitor and Application Insights, where alerts can be configured. Each rule scores up to 100 responses per hour by default; excess runs are skipped, and the documentation cited does not specify how responses are selected. Live traffic lacks reference answers, so the text recommends reference-free evaluators; ground-truth checks belong in scheduled evaluations on fixed datasets. Scores arrive after an action and report or alert rather than block it. The article describes Lyzr Opencontroller as adding request-path controls and release promotion gates, including support for externally hosted agents instrumented with OpenTelemetry.

### Source excerpt

TL;DR An IT service-desk agent passed every pre-launch evaluation (a composite scenario). Five weeks into production, the backend team renamed a field in the ticketing...

## ROSMonitoring in Action: Runtime Monitoring and Enforcement for ROS 2 Actions

DevFeed: [ROSMonitoring in Action: Runtime Monitoring and Enforcement for ROS 2 Actions](<https://devfeed.tech/articles/rosmonitoring-in-action-runtime-monitoring-and-enforcement-for-ros-2-actions-140025.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.22407>)

Author: Giacomo Paltrinieri (University of Modena,Reggio Emilia), Angelo Ferrando (University of Modena,Reggio Emilia)

Published: 2026-11-18T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Monitoring & Alerting](<https://devfeed.tech/topics/monitoring-alerting.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [acceptance](<https://devfeed.tech/tags/acceptance.md>), [actions](<https://devfeed.tech/tags/actions.md>), [applications](<https://devfeed.tech/tags/applications.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [behaviour](<https://devfeed.tech/tags/behaviour.md>), [but](<https://devfeed.tech/tags/but.md>), [cancellation](<https://devfeed.tech/tags/cancellation.md>), [communication](<https://devfeed.tech/tags/communication.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-lo](<https://devfeed.tech/tags/cs-lo.md>), [cs-ro](<https://devfeed.tech/tags/cs-ro.md>), [events](<https://devfeed.tech/tags/events.md>), [existing](<https://devfeed.tech/tags/existing.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [ros](<https://devfeed.tech/tags/ros.md>), [ros-2](<https://devfeed.tech/tags/ros-2.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [runtime-monitoring](<https://devfeed.tech/tags/runtime-monitoring.md>)

### AI overview

ROSMonitoring is extended to monitor and enforce ROS 2 action protocols, whose lifecycle includes goal submission, feedback, results, and cancellation. Actions are configured directly and instrumented through ROS 2 communication endpoints; the monitor correlates events by goal ID, tracks active goals, and can reject or cancel goals, suppress messages, or generate protocol-compliant responses when forwarding is impossible. Controlled stress tests found monitoring cost grew approximately linearly with repeated invocations at fixed workload, with added overhead from larger workloads and more client-server pairs. Findings describe sequential workloads; the current synchronous implementation is identified as a performance limitation.

### Source excerpt

arXiv:2611.22407v1 Announce Type: new Abstract: Robotic applications often rely on long-running operations, such as navigation, manipulation, and inspection, which in ROS~2 are commonly implemented as actions. Unlike topics and services, actions involve a structured lifecycle comprising goal submission and acceptance, feedback, status updates, result retrieval, and cancellation. Existing versions of ROSMonitoring support topics and services, but do not reconstruct this lifecycle or expose action-level events to a runtime-verification oracle. In this paper, we extend ROSMonitoring with runtime monitoring and enforcement for ROS~2 actions. Actions are declared directly in the monitoring configuration and automatically instrumented through the underlying ROS~2 communication endpoints. The generated monitor reconstructs action-level events, correlates them through goal identifiers, maintains the state of active goals, and translates violations into protocol-aware enforcement operations. These include goal rejection, cancellation, message suppression, and protocol-compliant responses generated directly by the monitor when the original communication cannot be forwarded. We evaluate the implementation through controlled stress tests that vary the number of action invocations, workload size, and clientâEUR "server topology. The results show approximately linear growth in monitoring cost with repeated action invocations under a fixed workload, while larger action workloads and a greater number of configured clientâEUR "server pairs introduce additional overhead. These results characterise the scaling behaviour of the current implementation under the tested sequential workloads while highlighting the main performance limitations of the current synchronous implementation.

## Bring Datadog BYOC to your on-premises data with MinIO AIStor

DevFeed: [Bring Datadog BYOC to your on-premises data with MinIO AIStor](<https://devfeed.tech/articles/bring-datadog-byoc-to-your-on-premises-data-with-minio-aistor-142007.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/datadog-byoc-minio-aistor/>)

Author: Sarjeel Yusuf; Anusha Podila

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [datadog](<https://devfeed.tech/topics/datadog.md>), [MinIO](<https://devfeed.tech/topics/minio.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [bits ai](<https://devfeed.tech/topics/bits-ai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [balance](<https://devfeed.tech/tags/balance.md>), [bits](<https://devfeed.tech/tags/bits.md>), [bits-ai](<https://devfeed.tech/tags/bits-ai.md>), [bring-your-own-cloud](<https://devfeed.tech/tags/bring-your-own-cloud.md>), [byoc](<https://devfeed.tech/tags/byoc.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [log-management](<https://devfeed.tech/tags/log-management.md>), [logs](<https://devfeed.tech/tags/logs.md>), [minio](<https://devfeed.tech/tags/minio.md>), [minio-aistor](<https://devfeed.tech/tags/minio-aistor.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [on-prem](<https://devfeed.tech/tags/on-prem.md>), [on-premises](<https://devfeed.tech/tags/on-premises.md>), [search](<https://devfeed.tech/tags/search.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

Datadog BYOC for Logs pairs Datadog's in-cluster indexing and search with MinIO AIStor object storage on infrastructure the organization controls. Observability Pipelines workers collect and process logs; indexers write searchable files to an AIStor bucket, while a PostgreSQL metastore tracks their locations and background compaction merges smaller files. Storage, indexing and search capacity can scale independently. Datadog searchers initiate TLS-encrypted outbound connections, authenticated with a Datadog API key, to query the on-premises data without inbound ports or a public endpoint. Log Explorer results pass through Datadog services for display but, according to the excerpt, are not stored or cached there; the indexed dataset stays in AIStor. The excerpt also describes RBAC, consent controls for Datadog support access, and disabling log samples or excluding log fields from notifications as privacy controls. AIStor erasure coding and object tiering support retention and storage-budget tradeoffs. BYOC currently supports logs; trace and metric support is described as coming soon.

### Source excerpt

Learn how Datadog BYOC and MinIO AIStor work together to help you search, monitor, and investigate logs while keeping your telemetry on-premises.

## Reducing database incident MTTR by 73% with a custom AWS DevOps Agent Skill

DevFeed: [Reducing database incident MTTR by 73% with a custom AWS DevOps Agent Skill](<https://devfeed.tech/articles/reducing-database-incident-mttr-by-73-with-a-custom-aws-devops-agent-skill-139360.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/reducing-database-incident-mttr-by-73-with-a-custom-aws-devops-agent-skill/>)

Author: Chetan Suri

Published: 2026-11-17T22:27:48Z

Content type: tutorial

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>)

Tags: [agent-skill](<https://devfeed.tech/tags/agent-skill.md>), [aws](<https://devfeed.tech/tags/aws.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [database](<https://devfeed.tech/tags/database.md>), [decision](<https://devfeed.tech/tags/decision.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [mttr](<https://devfeed.tech/tags/mttr.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [reduction](<https://devfeed.tech/tags/reduction.md>)

### AI overview

A custom AWS DevOps Agent Skill uses signal classification and a prioritized decision tree to guide Aurora PostgreSQL incident investigations across five failure modes: connection exhaustion, replication lag, slow query regression, storage pressure, and parameter drift. In a controlled internal test of three simulated incidents, average time to identify root cause fell from 52 to 14 minutes, and wrong hypotheses per incident fell from 3.0 to 0.3. The comparison covered connection exhaustion, slow query regression, and parameter drift, so the reported results do not establish performance across every branch or production conditions. The guide requires an AWS account and Agent Space access to the cluster, CloudWatch metrics and Performance Insights, and the Operator Web App; it recommends deploying for Incident RCA and On-demand agents, excluding Incident Triage because the procedure is too thorough for fast triage.

### Source excerpt

Database incidents routinely take 45 to 60 minutes to triage. This post shows how to build a custom AWS DevOps Agent Skill that encodes expert Aurora PostgreSQL triage into decision-tree logic across five failure modes, cutting mean time to resolution from 52 minutes to 14 minutes (a 73% reduction) in a controlled test.

## Use query statistics to find slow and expensive queries in Aurora DSQL

DevFeed: [Use query statistics to find slow and expensive queries in Aurora DSQL](<https://devfeed.tech/articles/use-query-statistics-to-find-slow-and-expensive-queries-in-aurora-dsql-138653.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/use-query-statistics-to-find-slow-and-expensive-queries-in-aurora-dsql/>)

Author: Rakesh Reddy Kondakindi

Published: 2026-11-17T21:09:25Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [application](<https://devfeed.tech/tags/application.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [build](<https://devfeed.tech/tags/build.md>), [change](<https://devfeed.tech/tags/change.md>), [code](<https://devfeed.tech/tags/code.md>), [cost](<https://devfeed.tech/tags/cost.md>), [dpu](<https://devfeed.tech/tags/dpu.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [help](<https://devfeed.tech/tags/help.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [index](<https://devfeed.tech/tags/index.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [latency](<https://devfeed.tech/tags/latency.md>), [performance](<https://devfeed.tech/tags/performance.md>), [post](<https://devfeed.tech/tags/post.md>), [queries](<https://devfeed.tech/tags/queries.md>), [query](<https://devfeed.tech/tags/query.md>), [statistics](<https://devfeed.tech/tags/statistics.md>)

### AI overview

Aurora DSQL query statistics record per-statement calls, latency, rows returned and scanned, compute and storage time, and DPU use, complementing sampled DASH metrics. In the walkthrough, CloudWatch Database Insights and Query Studio identify an order-history query scanning about 5.17 million rows to return 20, taking about 12 seconds and 656 DPU per call. EXPLAIN ANALYZE VERBOSE confirms a missing customer_id index. Building an index asynchronously lets the query read matching rows in created_at order and stop after 20; measured latency falls below 3 ms and DPU use to 0.015 per call. Statement statistics must be enabled per cluster and, in multi-Region setups, for each peer cluster. The post's figures come from a reproducible test; its DPU cost example uses US West (Oregon) pricing.

### Source excerpt

When a code change slows your application, Amazon Aurora DSQL query statistics help you find the slow and expensive queries behind it, down to the exact SQL statement. This post walks through a performance investigation that pinpoints a missing index, fixes it with an asynchronous index build, and measures the improvement in latency and DPU cost.

## Replit's agent swarms built an app monitoring platform in 2 days on a $3K budget. Now, it's offering them to customers.

DevFeed: [Replit's agent swarms built an app monitoring platform in 2 days on a $3K budget. Now, it's offering them to customers.](<https://devfeed.tech/articles/replit-s-agent-swarms-built-an-app-monitoring-platform-in-2-days-on-a-3k-budget-now-it-s-offering-them-to-customers-138248.md>)

Original publisher: [Read original article](<https://thenewstack.io/replit-missions-agent-swarms/>)

Author: Paul Sawers

Published: 2026-11-17T17:37:13Z

Content type: news

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Repl.it](<https://devfeed.tech/topics/replit.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-engineering](<https://devfeed.tech/tags/ai-engineering.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [application-monitoring](<https://devfeed.tech/tags/application-monitoring.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [compute](<https://devfeed.tech/tags/compute.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [platform](<https://devfeed.tech/tags/platform.md>), [replit](<https://devfeed.tech/tags/replit.md>)

### AI overview

Replit Missions lets users delegate an objective to AI agent swarms by setting success criteria, a spending limit, and actions that need human approval; agents choose and adapt their plan, while a separate agent checks results and can request revisions. Agents work in isolated cloud environments, and changes are merged with conflict handling. Replit says Missions built its Radar monitoring platform in two days for $3,000; in a deliberate database fault test, Radar alerted in 38 seconds against a 60-second target. The company also reports speedups of up to 19 times on selected NumPy workloads using 32 agents. These are company-reported results. Swarms can duplicate work, incur costs, and hit diminishing returns when tasks offer little parallel work. Replit says spending limits block further paid services when reached and infrastructure controls restrict integrations and require approval for specified actions. The article also recounts a 2025 incident in which a coding agent deleted a production database.

### Source excerpt

Agent swarms are all the rage, as companies set about finding ways to coordinate multiple AI agents to tackle complex The post Replit's agent swarms built an app monitoring platform in 2 days on a $3K budget. Now, it's offering them to customers. appeared first on The New Stack.

## Is your OpenTelemetry pipeline becoming a performance bottleneck?

DevFeed: [Is your OpenTelemetry pipeline becoming a performance bottleneck?](<https://devfeed.tech/articles/is-your-opentelemetry-pipeline-becoming-a-performance-bottleneck-140139.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/11/17/is-your-opentelemetry-pipeline-becoming-a-performance-bottleneck/>)

Author: Diana Todea (CNCF Ambassador, OpenTelemetry Documentation approver, Romanian Localization maintainer)

Published: 2026-11-17T12:21:00Z

Content type: article

Language: en

Sources: [Cloud Native Computing Foundation](<https://devfeed.tech/sources/cloud-native-computing-foundation.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [observability](<https://devfeed.tech/topics/observability.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [austria](<https://devfeed.tech/tags/austria.md>), [blog](<https://devfeed.tech/tags/blog.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [building](<https://devfeed.tech/tags/building.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [collecting](<https://devfeed.tech/tags/collecting.md>), [cost](<https://devfeed.tech/tags/cost.md>), [days](<https://devfeed.tech/tags/days.md>), [easy](<https://devfeed.tech/tags/easy.md>), [exploring](<https://devfeed.tech/tags/exploring.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [i](<https://devfeed.tech/tags/i.md>), [native](<https://devfeed.tech/tags/native.md>), [observability](<https://devfeed.tech/tags/observability.md>), [observability-pipelines](<https://devfeed.tech/tags/observability-pipelines.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [otel](<https://devfeed.tech/tags/otel.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>)

### AI overview

OpenTelemetry overhead comes from the whole pipeline, from instrumentation and attribute volume to polling, processing, export, and storage; its impact depends on workload, so a single overhead percentage is misleading. The source recommends benchmarking CPU, memory, latency, throughput, telemetry volume, and loss while changing settings individually. Its Collector examples cover exporter batching (which can reduce export work but increase buffering and latency), removing unused resource attributes, lengthening receiver polling intervals where lower time resolution is acceptable, and sampling traces (with tail sampling adding memory and processing costs). It advises placing the memory limiter early for protection under pressure, while noting it can refuse data and does not replace capacity planning. For Kubernetes, it describes separating edge collection from gateway processing, planning queues and retries for outages, and routing each trace to the same instance for tail sampling. Telemetrygen isolates Collector behavior in synthetic experiments; real application instrumentation overhead requires a representative application environment.

### Source excerpt

At Cloud Native Days Austria 2026, I presented a talk called How to Defeat OTel's Silent Killer: The Performance Overhead, exploring a problem that is easy to overlook when building observability pipelines: the cost of collecting...

## An Alternative to Crawlers: Scalable P2P Network Monitoring Using the Network Scale-Up Method

DevFeed: [An Alternative to Crawlers: Scalable P2P Network Monitoring Using the Network Scale-Up Method](<https://devfeed.tech/articles/an-alternative-to-crawlers-scalable-p2p-network-monitoring-using-the-network-scale-up-method-137036.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.21330>)

Author: Juan Marcos Ramirez, Sergio D\\'iaz-Aranda, Leonhard Balduf, Antonio Fern\\'andez-Anta

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [P2P](<https://devfeed.tech/topics/p2p.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [approach](<https://devfeed.tech/tags/approach.md>), [area](<https://devfeed.tech/tags/area.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [based](<https://devfeed.tech/tags/based.md>), [case](<https://devfeed.tech/tags/case.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [changes](<https://devfeed.tech/tags/changes.md>), [crawlers](<https://devfeed.tech/tags/crawlers.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [network-monitoring](<https://devfeed.tech/tags/network-monitoring.md>), [p2p](<https://devfeed.tech/tags/p2p.md>), [scale](<https://devfeed.tech/tags/scale.md>), [scale-up](<https://devfeed.tech/tags/scale-up.md>), [up](<https://devfeed.tech/tags/up.md>), [using](<https://devfeed.tech/tags/using.md>)

### AI overview

A lightweight approach uses information in Kademlia routing tables and the Network Scale-Up Method (NSUM) to estimate global peer-to-peer network attribute distributions from a small set of nodes, as an alternative to resource-intensive full-network crawls. Evaluated on IPFS, the method was assessed using 360 full-network crawls collected over one month across simulated measurement scenarios and a deployment dataset from May 2026. The abstract reports that views from 10 nodes achieved normalized biases below 10% and closely tracked changes in network composition over time. The evidence is specific to this IPFS case study.

### Source excerpt

arXiv:2611.21330v1 Announce Type: new Abstract: \Ac{p2p} networks have remained an active area of research and development for decades. Originally used for data dissemination, they have later become instrumental to decentralized payment systems, blockchains, and Web3 applications. Since decentralization is a crucial property of these networks, they are continuously monitored to track attributes such as the geographical distribution of nodes, which serve as indicators of infrastructure concentration and resilience. However, monitoring typically relies on network crawls to derive accurate snapshots, which requires substantial computational and network resources. In contrast, \ac{nsum} is a statistical tool that estimates the prevalence of subpopulations based on responses to questions such as \enquote{How many people do you know in a specific group?} This work leverages the information embedded in Kademlia routing tables to develop a lightweight \ac{nsum}-based measurement and estimation framework that infers global network attribute distributions from a small set of nodes, offering an alternative to full-network crawls. As a case study, we evaluate our approach on \ac{ipfs}, a well-researched and widely used Web3 data storage and retrieval network. This is the first application of \ac{nsum} to decentralized network measurement. We evaluate our methodology on two datasets: the first comprises 360 full-network crawls collected over one month to assess our measurement-estimation approach across multiple simulated measurement scenarios, while the second dataset was collected through a deployment of the proposed lightweight measurement framework during May 2026. The results show that local Kademlia routing views, with only 10 nodes, preserve sufficient information to accurately estimate global attribute distributions, achieving normalized biases below \SI{10}{\percent} and closely tracking temporal changes in network composition.

## Your Kubernetes Knowledge Is Becoming Cheaper. Your Production Judgment Isn't.

DevFeed: [Your Kubernetes Knowledge Is Becoming Cheaper. Your Production Judgment Isn't.](<https://devfeed.tech/articles/your-kubernetes-knowledge-is-becoming-cheaper-your-production-judgment-isn-t-136242.md>)

Original publisher: [Read original article](<https://blog.devops.dev/your-kubernetes-knowledge-is-becoming-cheaper-your-production-judgment-isnt-cabf2adfc61a?source=rss----33f8b2d9a328---4>)

Author: Arvind Verma

Published: 2026-11-16T13:25:19Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>), [AIOps for Kubernetes](<https://devfeed.tech/topics/aiops-for-kubernetes.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bash](<https://devfeed.tech/tags/bash.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [ci-cd-pipeline](<https://devfeed.tech/tags/ci-cd-pipeline.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [commands](<https://devfeed.tech/tags/commands.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [decision](<https://devfeed.tech/tags/decision.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-engineer](<https://devfeed.tech/tags/devops-engineer.md>), [docker](<https://devfeed.tech/tags/docker.md>), [english](<https://devfeed.tech/tags/english.md>), [git](<https://devfeed.tech/tags/git.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [helm](<https://devfeed.tech/tags/helm.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [production](<https://devfeed.tech/tags/production.md>)

### AI overview

The article argues that AI is making configuration such as Kubernetes YAML, Terraform modules, and CI/CD pipelines cheaper to produce, while production judgment remains central to DevOps. It recommends narrowing investigations with evidence, checking the failure's scope and system layer, and treating dashboards as signals rather than proof of user health. Before restarting, rolling back, draining, scaling, or failing over, assess consequences and blast radius; under uncertainty, seek a safe next test. During incidents, communicate impact, hypothesis, evidence being checked, and next action. It also urges engineers to learn failure modes alongside tool mechanics. These are the article's recommendations, not a comparison of specific AI tools.

### Source excerpt

There was a time when knowing how to write Kubernetes YAML felt like a superpower. You knew Deployments. You knew Services. You knew ConfigMaps. You knew Ingress. You knew how to write a Helm chart without accidentally deleting half the cluster. You learned Terraform. You learned Jenkins. You learned Bash. You learned Prometheus queries. You spent years collecting tools, commands, syntax, and implementation patterns. And then AI showed up. Now you can describe what you want in plain English and get a Terraform module. Ask for a Kubernetes Deployment and you get YAML. Ask for a CI/CD pipeline and you get a pipeline. Ask for a Bash script and you get one. Ask for a PromQL query and, assuming the machines haven't collectively decided to punish humanity that day, you get something reasonably useful. 😄 So here's the uncomfortable question: If AI can increasingly handle implementation, what exactly becomes more valuable for a DevOps engineer? I think the answer is simple. Judgment. Not knowing more commands. Not memorizing more YAML. Not collecting another 47 certifications. Knowing what to do when the obvious answer doesn't work. And production has a beautiful way of ensuring that the obvious answer almost never works. 1 The Shift: From Tool Operator to Decision Maker For years, DevOps careers were heavily associated with tools. Learn AWS. Learn Docker. Learn Kubernetes. Learn Terraform. Learn Jenkins. Learn Ansible. Learn Prometheus. Learn Grafana. Learn Git. Learn Linux. And yes, these skills still matter. The tools aren't suddenly useless because AI can generate configuration for them. But something important is changing. The cost of producing configuration is falling. Consider a simple Kubernetes deployment. Previously, an engineer might spend time writing: apiVersion: apps/v1 kind: Deployment metadata: name: payment-api spec: replicas: 3 selector: matchLabels: app: payment-api template: metadata: labels: app: payment-api spec: containers: - name: payment-api image

## Killing a tempdb killer - Part 1

DevFeed: [Killing a tempdb killer - Part 1](<https://devfeed.tech/articles/killing-a-tempdb-killer-part-1-135973.md>)

Original publisher: [Read original article](<https://sqlperformance.com/2026/11/tempdb/killing-a-tempdb-killer-part-1>)

Author: Aaron Bertrand

Published: 2026-11-16T06:00:28Z

Content type: article

Language: en

Sources: [SQLPerformance.com](<https://devfeed.tech/sources/sqlperformance-com.md>)

Topics: [sql-server](<https://devfeed.tech/topics/sql-server.md>), [database monitoring](<https://devfeed.tech/topics/database-monitoring.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [monitoring](<https://devfeed.tech/tags/monitoring.md>), [rca](<https://devfeed.tech/tags/rca.md>), [risks](<https://devfeed.tech/tags/risks.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [sql-server](<https://devfeed.tech/tags/sql-server.md>), [tempdb](<https://devfeed.tech/tags/tempdb.md>)

### AI overview

The excerpt describes a self-contained SQL Server tempdb monitoring system designed to detect capacity risks early and preserve evidence for root-cause analysis. A view reports data and log usage, drive headroom, whether the next autogrowth can fit, and configuration warnings. A collector, intended to run about every ten seconds, stores lightweight snapshots and starts detailed session and growth capture when data or log free space falls below a configurable threshold (50% by default). It alerts at configured pressure levels and can terminate selected user sessions only when rule-specific checks and safeguards pass; log-related termination is observation-only unless enabled, and some log reuse candidates remain diagnostic when session attribution is ambiguous. The design uses the default trace for growth evidence when available, so that capture depends on the trace being enabled. It also retains monitoring history with cleanup rules, preserving significant session details and kill decisions longer for RCA.

### Source excerpt

Aaron Bertrand presents a practical SQL Server tempdb monitoring system that flags risks, captures pressure, preserves RCA evidence, and can safely stop runaway sessions. The post Killing a tempdb killer - Part 1 appeared first on SQLPerformance.com.

## Improve RDS Proxy multiplexing for PostgreSQL, Part 2: Diagnose and monitor

DevFeed: [Improve RDS Proxy multiplexing for PostgreSQL, Part 2: Diagnose and monitor](<https://devfeed.tech/articles/improve-rds-proxy-multiplexing-for-postgresql-part-2-diagnose-and-monitor-133438.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/improve-rds-proxy-multiplexing-for-postgresql-part-2-diagnose-and-monitor/>)

Author: Pavel Rabinovich

Published: 2026-11-13T21:08:04Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [insights](<https://devfeed.tech/tags/insights.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [regression](<https://devfeed.tech/tags/regression.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

CloudWatch metrics can show that RDS Proxy multiplexing has degraded, but enhanced proxy logs help explain why and which connections are involved. CloudWatch Logs Insights queries summarize backend connection borrows, releases, and pins, or trace one connection's lifecycle. For user and ApplicationName attribution, the post correlates proxy TCP events with PostgreSQL connection logs using IP:port; this is a best-effort match that depends on a narrow time window and synchronized timestamps. Healthy multiplexing shows many borrows and releases per backend connection, few pins, and substantially fewer backend than client connections. The post recommends alarms for sustained pinning and an elevated backend-to-client connection ratio, with workload-specific baselines and a traffic floor. Enhanced logging produces detailed SQL text, adds log volume, cost, and possible proxy overhead, so restrict log access, use it temporarily, and disable it after diagnosis.

### Source excerpt

Metrics alone can't always pinpoint what is reducing RDS Proxy multiplexing for PostgreSQL. Part 2 shows how to use Amazon CloudWatch Logs Insights with enhanced proxy logs to find the root cause, what healthy multiplexing looks like in metrics and logs, and how to set up CloudWatch alarms that catch regression.

## What it takes to ship a self-improving agent

DevFeed: [What it takes to ship a self-improving agent](<https://devfeed.tech/articles/what-it-takes-to-ship-a-self-improving-agent-133418.md>)

Original publisher: [Read original article](<https://montecarlo.ai/blog-ship-self-improving-agents>)

Author: Ruslan Sultanov

Published: 2026-11-13T19:54:30Z

Content type: article

Language: en

Sources: [Monte Carlo](<https://devfeed.tech/sources/monte-carlo.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [ai observability](<https://devfeed.tech/topics/ai-observability.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-trust](<https://devfeed.tech/tags/agent-trust.md>), [bayes](<https://devfeed.tech/tags/bayes.md>), [eval](<https://devfeed.tech/tags/eval.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [monte-carlo](<https://devfeed.tech/tags/monte-carlo.md>), [production](<https://devfeed.tech/tags/production.md>), [self-improving-agent](<https://devfeed.tech/tags/self-improving-agent.md>), [self-improving-agents](<https://devfeed.tech/tags/self-improving-agents.md>)

### AI overview

Production checks and guardrails catch anticipated failures, but agents can fail silently as users, data, models, tools, rate limits, and team changes shift. The article argues for a recurring production learning loop: join traces, eval results, tickets, and incident context; detect issues in real traffic; triage findings; trace root causes across agents and their data; propose a fix in the team's workflow; and verify it against later runs. Monte Carlo's Bayes illustrates this loop, with human involvement ranging from manual work to approval of proposed fixes or autonomous handling with exception escalation. To begin, review a month of incidents for one established agent, noting how each was detected and whether the fix was verified.

### Source excerpt

Most teams learn their agent is broken the same way: a customer tells them. In Monte Carlo's 2026 survey of 260 agent builders and leaders, 52% of builders said they find out about production issues through customer or user complaints. Those teams didn't skip the work. Their agents passed an eval suite, sat behind guardrails, ...

## What's new in Pyroscope: profile more of your workflows, troubleshoot with AI agents, and more

DevFeed: [What's new in Pyroscope: profile more of your workflows, troubleshoot with AI agents, and more](<https://devfeed.tech/articles/what-s-new-in-pyroscope-profile-more-of-your-workflows-troubleshoot-with-ai-agents-and-more-133569.md>)

Original publisher: [Read original article](<https://grafana.com/blog/whats-new-in-pyroscope-profile-more-of-your-workflows-troubleshoot-with-ai-agents-and-more/>)

Author: Tiffany Jernigan

Published: 2026-11-13T17:14:29Z

Content type: release

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Python](<https://devfeed.tech/topics/python.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [cli](<https://devfeed.tech/tags/cli.md>), [code](<https://devfeed.tech/tags/code.md>), [commands](<https://devfeed.tech/tags/commands.md>), [container](<https://devfeed.tech/tags/container.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [continuous-profiling](<https://devfeed.tech/tags/continuous-profiling.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-pyroscope](<https://devfeed.tech/tags/grafana-pyroscope.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [net](<https://devfeed.tech/tags/net.md>), [observability](<https://devfeed.tech/tags/observability.md>), [profile](<https://devfeed.tech/tags/profile.md>), [traces](<https://devfeed.tech/tags/traces.md>), [troubleshoot](<https://devfeed.tech/tags/troubleshoot.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Pyroscope adds memory profiling for Python and Rust, .NET profiling on Windows, and ways to inspect individual profiles and call paths. Python's SDK reports heavy allocations and memory still in use; Rust uses jemalloc to report live memory. Windows support is x64 and begins with profiler 1.3.0; .NET 8-10 offer the same profile types as Linux, while .NET Framework 4.7 and later support CPU and wall-time profiling. Windows support is in public preview. The gcx CLI can query Pyroscope profiles, rank services by resource use, list costly individual profiles (exemplars), inspect a selected profile, and export pprof files. Grafana also displays exemplars and adds an expandable Call Tree to trace paths to expensive functions. Exemplars require Pyroscope 2.0's v2 storage layer; Call Tree is available in Profiles Drilldown 2.3.0 and later, Explore, and the flame graph panel in Grafana 13.3, with a feature toggle required on earlier Grafana versions.

### Source excerpt

When an application slows down or memory usage keeps climbing, knowing which code is responsible can help you find a fix faster. Continuous profiling gives you that visibility, so you can see where your application spends resources such as CPU time and memory. We've made updates to Pyroscope, our open source continuous profiling database, that make it easier to profile your applications, find performance bottlenecks, and optimize your code, whether you're doing the work yourself or with an AI agent. Highlights include: Profile more of your workloads: Memory profiling for Python and Rust, and .NET support on Windows, helps you find performance bottlenecks across more of your services. Let AI agents work with your profiling data: Pyroscope commands in gcx, the Grafana CLI, let an agent query your profiles directly. See more of your profiling data in Grafana: Exemplars and a new Call Tree view help you explore your profiles visually, whether you're investigating on your own or looking at what an agent found. Many of these capabilities build directly on Pyroscope 2.0, the ground-up rearchitecture of Pyroscope that makes continuous profiling more cost-effective at scale (in our production environment, it reduced the symbol storage footprint by up to 95%). For example, exemplars require the v2 storage layer that Pyroscope 2.0 is built on. Read on to learn more about some of the latest updates. And for a full list of recent changes, see the release notes for Pyroscope and Profiles Drilldown. Profile more of your workloads Memory profiling and Windows support have been some of the most frequently requested features for Pyroscope. If you run Python or Rust services, you can now use the Pyroscope SDKs to see where their memory goes, not just their CPU time. If you run .NET applications on Windows, you can now profile those, too. Find memory leaks and heavy allocation: memory profiling for Python Memory issues can be hard to track down from metrics alone. A container's memory

## Google Open Sources Ambient Quality Agent (AQuA) to Diagnose Production AI Agent Failures

DevFeed: [Google Open Sources Ambient Quality Agent (AQuA) to Diagnose Production AI Agent Failures](<https://devfeed.tech/articles/google-open-sources-ambient-quality-agent-aqua-to-diagnose-production-ai-agent-failures-132341.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/google-ambient-agent-prod/>)

Author: Leela Kumili

Published: 2026-11-13T13:53:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic-ai-architecture](<https://devfeed.tech/tags/agentic-ai-architecture.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-architecture](<https://devfeed.tech/tags/ai-architecture.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [ambient](<https://devfeed.tech/tags/ambient.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [changes](<https://devfeed.tech/tags/changes.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [failure](<https://devfeed.tech/tags/failure.md>), [failures](<https://devfeed.tech/tags/failures.md>), [google](<https://devfeed.tech/tags/google.md>), [google-ambient-agent-prod](<https://devfeed.tech/tags/google-ambient-agent-prod.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [open](<https://devfeed.tech/tags/open.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [production](<https://devfeed.tech/tags/production.md>), [production-ai](<https://devfeed.tech/tags/production-ai.md>), [quality](<https://devfeed.tech/tags/quality.md>), [reference](<https://devfeed.tech/tags/reference.md>), [root](<https://devfeed.tech/tags/root.md>), [seat](<https://devfeed.tech/tags/seat.md>), [selection](<https://devfeed.tech/tags/selection.md>)

### AI overview

AQuA is an open-source reference implementation for finding recurring quality failures in production AI agent sessions and tracing verified issues to the deployed code or other causes. It runs outside the request path, samples up to 1,000 sessions from Cloud Trace, Cloud Logging, or BigQuery, and groups and verifies candidate findings against configurable criteria. For root cause analysis, it compares failures with an immutable deployment snapshot, cites relevant file lines, and can attribute issues to dependencies, handoffs, or retrieved data; it does not apply fixes or open pull requests. In a controlled replay of 32 travel-agent sessions, verification reduced 42 findings to six issues. After prompt changes, seat-check bypasses fell from 15 sessions to two, vegan-preference omissions from seven to zero, and sessions passing all checks rose from five to 13. These results were from replay, not production traffic. Sampling may miss rare failures, and replay may not reproduce external state.

### Source excerpt

Google has open-sourced AQuA, a reference implementation that analyzes production AI agent sessions, verifies recurring failure patterns, and investigates root causes against deployed source snapshots. In a 32-session replay, developers reduced seat selection bypasses from 15 sessions to two and dietary preference omissions from seven to zero after prompt changes. By Leela Kumili

## Continual Event Recognition for Autonomous Optical Network Monitoring

DevFeed: [Continual Event Recognition for Autonomous Optical Network Monitoring](<https://devfeed.tech/articles/continual-event-recognition-for-autonomous-optical-network-monitoring-133068.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.16038>)

Author: Khouloud Abdelli

Published: 2026-11-13T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [communications](<https://devfeed.tech/topics/communications.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [few-shot](<https://devfeed.tech/topics/few-shot.md>)

Tags: [autonomous](<https://devfeed.tech/tags/autonomous.md>), [composition](<https://devfeed.tech/tags/composition.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [detection](<https://devfeed.tech/tags/detection.md>), [event](<https://devfeed.tech/tags/event.md>), [events](<https://devfeed.tech/tags/events.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [few-shot](<https://devfeed.tech/tags/few-shot.md>), [integration](<https://devfeed.tech/tags/integration.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [network-monitoring](<https://devfeed.tech/tags/network-monitoring.md>), [open](<https://devfeed.tech/tags/open.md>), [optical](<https://devfeed.tech/tags/optical.md>), [optical-networks](<https://devfeed.tech/tags/optical-networks.md>), [polarization](<https://devfeed.tech/tags/polarization.md>), [prototype](<https://devfeed.tech/tags/prototype.md>), [prototypes](<https://devfeed.tech/tags/prototypes.md>), [reasoning](<https://devfeed.tech/tags/reasoning.md>), [recognition](<https://devfeed.tech/tags/recognition.md>), [testbed](<https://devfeed.tech/tags/testbed.md>)

### AI overview

The framework adapts SOP-based optical network monitoring to new disturbances without encoder retraining, using prototype representations, open-set recognition, and few-shot prototype registration. On a 2600-km ROADM-based testbed, it achieved 99.82% closed-set recognition accuracy and integrated novel events. Overlapping disturbances showed differing degrees of latent compositionality: some were recognized zero-shot by composing existing prototypes, while others required few-shot registration.

### Source excerpt

arXiv:2611.16038v1 Announce Type: new Abstract: Autonomous optical networks require monitoring systems capable of adapting to evolving disturbances without repeated retraining or service interruption. We propose a continual event recognition framework for state-of-polarization (SOP)-based optical monitoring based on prototype representations, open-set recognition, and few-shot prototype registration. The framework supports recognition of known disturbances, detection and integration of novel events, and investigates whether overlapping disturbances can be inferred through compositional reasoning from existing prototypes. Experimental validation on a 2600-km ROADM-based optical testbed demonstrates 99.82% closed-set recognition accuracy, successful adaptation to novel disturbances without encoder retraining, and reveals that overlapping optical disturbances exhibit varying degrees of latent compositionality. While some overlaps can be recognized in a zero-shot manner through prototype composition, others require explicit few-shot registration. These results establish continual event recognition as a promising paradigm for future autonomous optical network monitoring systems.

[Next page](<https://devfeed.tech/topics/monitoring.md?cursor=WyIyMDI2LTExLTEzVDA1OjAwOjAwKzAwOjAwIiwgIjVkYTcwNzE5LTk1MWYtNDJhNy1iNWMwLWJjMzdhOWVmZmJkNCJd>)