Traversal announced the general availability of Incident Workers, the public beta of Alert Workers, and the launch of the Workers console—a web surface for deploying and managing a full fleet of agents. Together, they provide a proactive system that supports enterprise teams investigating incidents and triaging alerts.
An Incident Worker is a proactive AI SRE that joins an incident channel the moment something breaks, decides for itself when to engage, and owns the investigation end to end. It runs on Traversal's Causal Search Engine™ and Production World Model™, the same foundation behind the rest of the platform, so it carries out a real investigation rather than wrapping a chat interface around telemetry.
Alert Workers, now in public beta, bring the same intelligence to noisy alert channels. An Alert Worker learns which alerts are routine, reasons across signals, dedupes repetitive noise, and surfaces the handful that are new or meaningful, with the reasoning attached. Teams steer it in plain English, with instructions like "only page me on Sev1 and Sev2" or "ignore anything from staging." The result is fewer false pages, faster detection, and more incidents avoided before they start.
The Workers console gives teams one place to deploy and manage their fleet. Engineers can see every Worker across every channel, open any one to read its live synthesis of the incident, and ask it questions in private chat without adding channel noise. When there is no channel yet, they can start a shared Worker session from the web.
Incident Workers are generally available now.
Alert Workers are available in public beta.
Both run inside Slack and Microsoft Teams; and are available on the new Traversal Workers console, with no prompting or configuration required.
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 ...