For years, the promise of observability has often been stifled by the reality of fragmented workflows. Engineering teams frequently find themselves trapped in a cycle of manual dashboard maintenance, context-switching between disparate monitoring tools, and loss of critical information when incidents escalate across organizational boundaries. Amazon Web Services (AWS) is looking to break this cycle with the launch of Amazon CloudWatch Omni, a new, purpose-built observability experience designed to unify team collaboration and intelligence.
Launched on September 22, 2026, CloudWatch Omni shifts the observability paradigm from infrastructure-centric monitoring to an application-centric, collaborative workspace. By moving away from a collection of isolated signals toward a consolidated view of application health, AWS aims to streamline the incident response process and reduce the cognitive load on site reliability engineers (SREs) and developers alike.
### Breaking the Console Barrier
Perhaps the most significant structural change introduced by Omni is its accessibility. Eschewing the traditional AWS Management Console in favor of a dedicated, identity-provider-integrated web application, Omni allows teams to collaborate without requiring individual AWS access permissions. By leveraging IAM Identity Center, organizations can grant access through existing enterprise single sign-on (SSO) providers—such as Okta or Azure AD—ensuring that developers, database engineers, and managers are all operating within the same secure environment.
This unified space is built upon OpenTelemetry. For existing CloudWatch users, the transition is seamless: telemetry data, logs, metrics, and traces are automatically available in the new interface without requiring re-instrumentation. For workloads outside the AWS ecosystem, OTLP (OpenTelemetry Protocol) endpoints allow teams to ingest data directly into Omni, providing a centralized “single pane of glass” across diverse environments.
### Intelligence at the Center of Investigation
At the core of the CloudWatch Omni experience is the integration of the Amazon DevOps Agent. Designed to act as an active participant in troubleshooting, the agent uses the same telemetry stream as human engineers. During an incident, the agent doesn’t just surface errors; it correlates related events across the application topology, identifies potential root causes by tracing dependency paths, and suggests actionable mitigation steps.
This intelligence is applied to an automatically generated application map. Omni continuously discovers services and their dependencies, meaning that as application architectures evolve, the observability topology updates in real-time. This dynamic mapping eliminates the need for teams to manually curate and maintain static dashboards, allowing them to focus on high-level availability targets and latency budgets instead.
### A Workflow-First Approach
During a typical incident, Omni facilitates a hand-off of context that was previously difficult to maintain. If an alarm triggers—for example, due to elevated error rates in a checkout service—Omni presents a pre-loaded session containing the service topology, recent deployments, and the DevOps Agent’s initial findings. As engineers from different teams join the session, they inherit the full investigation history, ensuring that no context is lost in fragmented communication channels like Slack or email threads. Once an incident is resolved, the session is archived automatically, serving as a comprehensive post-incident record.
For organizations heavily invested in the next generation of software development, Omni also provides specialized support for generative AI and agentic workloads. By offering trace exploration and evaluation frameworks, the platform allows teams to monitor the performance of AI agents alongside the applications that host them.
CloudWatch Omni represents a fundamental evolution in how AWS approaches operational visibility. By combining centralized access, automatic dependency mapping, and integrated AI-driven analysis, AWS is effectively moving observability out of the background and into the heart of the collaborative development lifecycle.
Source: AWS News Blog
