Honeycomb.io announced new features designed to help DevOps and engineering teams find and fix issues in production before their customers do.
The release introduces Honeycomb's new AI Ecosystem, which provides a fleet-wide view of all of your AI agents in production, their performance, costs and individual conversations, while new Canvas MCP connectors bring context to your telemetry data.
"Teams are shipping agents faster than they can see what those agents are doing," said Graham Siener, SVP of Product at Honeycomb. "You can't govern what you can't see. AI Ecosystem gives you one view of failure rates, costs, and behaviors of every agent you run, including the ones that haven't caught fire yet. Even better, it also allows you to go straight down to the conversation that caused an issue. When something needs a closer look, Canvas connectors put the code, tickets and team discussion right next to the telemetry, instead of scattered across five other tools."
Honeycomb's AI Ecosystem gives teams a diagnosis layer for an entire fleet of agents in production, providing a continuous, aggregate assessment on failure rates, token usage, latency, and cost across every agent. Because it's built on Honeycomb's high-cardinality data model, teams can drill down into individual agent conversations seamlessly from a high-level fleet view.
At launch, AI Ecosystem contains three core features, including Agent Fleet Performance, LLM Cost Tracking, and Agent Conversations (previously known as Agent Timeline). These collective capabilities provide full context and dynamic granularity on fleet-level health, per-agent health and volume, cost and efficiency, latency and performance, and blast radius.
To help teams respond faster, Honeycomb is expanding Canvas, its multiplayer workspace, with new MCP connectors. These connectors provide context beyond production telemetry. They add details like source code, IT and support tickets, design rationale, live team conversations and more. Connectors available today include GitHub, Linear, Pylon, incident.io, Atlassian, Braintrust, Sentry, Amplitude, and Checkly.
Unlike single-user, chat-based agents, Canvas allows teams to work collaboratively to view the same telemetry artifacts, edit queries, verify agent prompts, check tool invocations and more. It's designed for the realities of investigating complex production environments, where teams of humans and agents need to operate off of shared context.
The Canvas MCP connectors are available now.
AI Ecosystem is in early access now, with general availability anticipated by the end of this year or early next.
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 ...