AWS introduced Amazon CloudWatch Omni.
CloudWatch is the foundation of how teams operate on AWS – it processes trillions of observability signals daily for millions of active customers across every industry and region. Amazon CloudWatch Omni is the next generation of CloudWatch: unified observability bringing your applications and the AI agents running alongside them into one reimagined off-console experience, with auto-discovered topology, natural language and SQL queries, and AI-guided investigation powered by AWS DevOps Agent across both.
CloudWatch Omni helps address some of the biggest observability challenges teams face today:
- Ship agents you can trust: Eval-driven observability that answers "why did my agent do that?", not just "is it running?" Developers trace agent behavior, evaluate quality continuously, and run experiments to validate fixes before they ship. This works across frameworks (CrewAI, LangGraph, OpenAI Agents SDK, Strands, Vercel AI SDK, and more) and meets developers where they already work: an Omni IDE extension for VS Code, Cursor, and Kiro, plus a dedicated Omni web experience for production.
- See applications as customers do: Understand applications as your customers see them, not as disconnected resources. You work in an Omni space (a workspace built around an application, team, or set of workloads), where everything organizes around your services, user journeys, and business transactions, with auto-discovered topology, fleet dashboards, golden metrics, and native alerting in one place. It ingests application and agent telemetry from Azure today, with other cloud providers coming soon.
- Correlate across the full stack: Agents call APIs, depend on services, and run on infrastructure. When something breaks, the root cause might be the agent's reasoning, a stale knowledge base, or a latency spike in a downstream service. Omni is built on the CloudWatch unified data store (the telemetry store already trusted by millions of customers), so it correlates agent behavior to application health to infrastructure in one experience.
- Investigate with AI: Intelligence runs through the whole Omni experience. Instead of navigating an account-and-region maze, every investigation starts from a plain-language question rather than a dashboard you built and maintained. You get a built-in AI assistant that handles discovery and guided investigation, enables natural language queries, and native AWS DevOps Agent (an AI agent that investigates operational issues) automatically correlates data and identifies the root cause across agents, applications, and infrastructure.
- Work in one place: Omni shifts your day from hunting across tools and switching context to asking questions and resolving incidents in a single experience. It lives outside the AWS Console entirely with its own UI and access model: a dedicated web experience for operators and a native IDE extension for VS Code, Cursor, and Kiro, so developers see agent traces the moment they run locally.
For developers, that means staying in your workflow. For operators, it means the end of screen-hopping.
CloudWatch Omni works across frameworks (LangGraph, CrewAI, OpenAI Agents SDK, Vercel AI SDK, Strands, and more). A native extension for VS Code, Kiro, and Cursor surfaces traces the moment you run your agent locally, while operators work from an off-console web experience with enterprise SSO. Both surfaces share one data layer, so when an operator spots a regression, a developer opens that exact trace in their IDE and starts fixing it.
Teams building on Amazon Bedrock AgentCore, a managed platform for building, deploying, and scaling AI agents, get native observability automatically, with telemetry flowing into CloudWatch Omni the moment you enable it. AgentCore's built-in evaluators for retrieval quality, tool selection, guardrail enforcement, and memory coherence are available in Omni out of the box, and if you already use AgentCore Observability (the built-in telemetry for agents running on the AgentCore runtime), CloudWatch Omni extends that experience into your IDE and a standalone web UI with your existing instrumentation carried forward. Teams using independent evaluation tools like Braintrust, DeepEval, or Ragas can bring those evaluators into CloudWatch Omni directly and keep their existing investment.
When an agent produces a bad result, the cause can live anywhere in the chain, and in CloudWatch Omni agent traces and application telemetry share one data layer so you can follow it. The agent's decision ("called tool X, got a bad result") connects to the application signal ("that API returned an error because the backing service hit a capacity limit") connects to the infrastructure metric ("the database connection pool was exhausted"), and you follow the thread from top to bottom in one investigation.
CloudWatch Omni auto-discovers your application topology and organizes telemetry around services, dependencies, and the traffic flowing between them. You start from the application as a whole, then drill into the specific service, trace, or log line that matters. For existing CloudWatch customers, the path is immediate. Telemetry you already send to CloudWatch (logs, metrics, and traces) becomes available in Omni through a unified data store that enables correlated analysis across all signal types, with no reconfiguration required. Your existing instrumentation, dashboards, and alarms carry forward, and Omni extends what you already have into a new, application-centric experience. For teams new to CloudWatch, onboarding is just as straightforward: send telemetry via OpenTelemetry (OTLP) endpoints, create a CloudWatch Omni space, and Omni auto-discovers your topology and begins surfacing dependencies and health signals immediately.
Omni’s built-in AI assistant lets you describe what you're seeing in natural language, then identifies anomalies, suggests hypotheses, and walks you through the investigation. Unified search lets you query across logs, metrics, and traces in one place using natural language or SQL. Alerts trigger on conditions across any signal type, and Slack and GitHub integrations route those signals to your team where they already work. CloudWatch Omni supports ingesting application and agent telemetry from Azure environments today, with deeper multi-cloud observability coming soon. Org-level domains, enterprise SSO, and fine-grained permissions mean your entire organization onboards through one setup, with each person seeing data scoped to their role.
Agent developers: Install the CloudWatch Omni extension from the VS Code Marketplace (free, no AWS account needed for local development), instrument your agent via OTLP, and run it to explore traces, evaluations, and experiments right away.
Application teams: Create a CloudWatch Omni space to organize your services and team access. If you already use CloudWatch, your logs, metrics, and traces are there with zero reconfiguration. If you're starting fresh, send telemetry via OTLP and Omni auto-discovers your topology and health signals immediately.
The Latest
For decades, traditional observability tools have forced IT professionals to sift through endless dashboards, turning a flood of alerts into actionable insight and driving widespread burnout. While enterprises adopted AI to eliminate this friction, most still deploy it reactively rather than proactively ... As systems become more complex and IT moves to the center of business strategy, a reactive posture is unsustainable ...
Ask an operations team what they monitor and you will hear a familiar list: latency, errors, throughput, uptime. Those signals still matter for AI, but they no longer answer the most important question. As Krishna Sai, CTO of SolarWinds, puts it: "Traditional observability tells you a system is running. AI observability tells you whether it's still reasoning soundly. Those are completely different questions" ...
AI observability serves several roles across an organization. AI engineers use it to build, evaluate, and improve AI systems. SREs use it to operate those systems reliably and efficiently in production, including managing their cost. Leaders need it to connect AI behavior and operational performance to business outcomes. The common need is a clear understanding of whether AI systems are delivering the intended result ...
Part 4 outlines the challenges enterprise face when adopting AI observability. The main challenge is that AI complexity compounds at every stage of maturity. LLM-based applications introduce new behavior, dependencies, and quality considerations, while Agentic AI adds further failure modes as systems make decisions and take actions ...
Part 3 reports on the current state of AI observability. Most experts agree: enterprises are moving faster with AI than they are with the operational discipline needed to run it safely ...
When discussing AI Observability, one of the first questions that arises: Is this just an extension of traditional observability or is this a whole new type of tool? Part 2 compares traditional observability with AI observability ...
In this extensive 14-part series that will post over the next three weeks, experts across observability and AI will provide insight and opinions on the need for AI Observability, the challenges, the benefits, the current state, and predictions for the future ...
Amid rising complexity, organizations are moving quickly toward agent-driven operations: AgenticOps, according to The Impact of Agentic AI on Network Operations, a new report from Cisco ...
AI, automation, and enterprise software give organizations an extraordinary amount of leverage. Work that once required hours can happen in minutes. Information buried across systems can be analyzed almost instantly. Complex workflows can be coordinated across teams with far less manual intervention. That leverage creates a temptation to start with the technology ...
Everyone wants to talk about models. Compute clusters. Benchmark scores that climb a fraction of a point and make headlines anyway. It's an easy conversation to have because it's measurable. But it's also increasingly beside the point ...