|
By Moses Mendoza
This post was co-written with Staff Software Engineer Martin Holman. Honeycomb Canvas is a collaborative investigation environment. When something goes wrong in production, multiple engineers might join the same Canvas to debug it together. Each person has their own AI agent, so they can pursue their own conversation thread and line of inquiry. This creates an opportunity for coordination.
|
By Moses Mendoza
"Hello world, this is your agent speaking!" The agent loop! The LLM is calling tools, the answers are sensible, and the sky's the limit. Now, as you look forward to production, you look for a composable toolset, something that can grow with your use case and system needs. That's what we created with Honeycomb Canvas: a collaborative investigation space where AI agents help you understand, fix, and learn about your system.
|
By Reid Savage
As of today, I’ve drafted this post upwards of 10 times – it’s old enough that the version I first started working on was called “Reflections on 1 Year of SRE Management” (I’m currently at 2.5 years). But everything I learned during that first year became critical for the next.
|
By Rox Williams
At O11yCon, we talked to engineering teams across the industry, and the numbers are starting to get genuinely wild: Mixpanel DevOps Engineer Eddie Bracho told us their engineering team is generating 50% more PRs than before AI came into the mix (sorry). That kind of velocity is exciting, but it's also a pressure test for every part of your stack that isn't writing code, including your observability practice. Here's what we're hearing from customers about how that's playing out.
|
By Dan Juengst
AI agents are nondeterministic, multi-step, and opaque. When one fails in production, "the model said something weird" is the cheapest, most useless line in your incident postmortem. To debug agents the way they actually run, you need telemetry that captures all of it, in order, with enough context to reconstruct what happened. The OpenTelemetry GenAI Semantic Conventions give you a vendor-neutral way to do exactly that.
|
By Charity Majors
IT’S HERE it’s here it’s here it’s here!!!! The second edition of Observability Engineering is available for download, and since Honeycomb is the sponsor, you can now download it from our website (the dead tree version will take another month). This is a strange time to be writing a book.
|
By Dan Juengst
A few weeks ago I wrote about a customer’s refund request that stopped halfway through at 11:47 p.m. on a Tuesday night. That post walked through the 40 minutes it took to work out what happened when an agentic application had a problem: a tool retried against a rate-limited payments API, the error responses filled up the context window, and the agent gave up. The whole reason we built Agent Timeline was to turn that 40 minutes into five. To reduce MTTR. To solve the problem and get back to sleep.
|
By Colin Burke
Observability has always been important, and much like any core capability in your business, the value needs to be understood. For years, the value of observability was predictable. It was uptime, error rates, MTTR, and likely tool consolidation. That was enough to be able to show progress. These are foundational, tablestakes metrics—and they still matter, but they aren’t enough.
|
By Liz Fong-Jones
This is the fourth installment in the Graviton retrospective series we've been writing since 2021. The methodology is the same one I always reach for: hold the workload constant, run both generations on the same Kubernetes namespace concurrently, and let the per-pod numbers speak.
The OpenTelemetry Collector is usually deployed as a long-running process: a sidecar, a DaemonSet, an EC2 instance, a docker container on my computer. It sits there listening for telemetry. That's fine when I want to send telemetry all day, but not when telemetry is rare. Like right now, when I have an agent defined on AgentCore, and it runs a few times a week maybe. Or my website that hardly sees any traffic. Can I run the OpenTelemetry Collector as a Lambda function?
|
By Honeycomb
At Slack, between 100 to 200 users per day use Honeycomb for client observability, tracing, instrumentation, analysis of performance, frontend issues, investigating incidents, or just looking into production issues.
|
By Honeycomb
Watch Nathen Harvey's full talk at O11yCon 2026, Honeycomb's observability conference, and enjoy Christine Yen's intro as well.
|
By Honeycomb
In this demo, Liz and Kale talk through a slow query that Liz couldn't get out of her head. During a conference, she set out to solve it... and ended up finding two more bugs to fix with, Honeycomb MCP, and Honeycomb Canvas.
|
By Honeycomb
In her talk at O11yCon 2026, Nishi Bhonsle of Salesforce talked about,, and provided some great examples of how Honeycomb has helped Salesforce issues in seconds. Here's a 4-minute highlight reel.
|
By Honeycomb
Honeycomb has shipped a production integration with Amazon Bedrock AgentCore, surfacing agent telemetry directly in Agent Timeline, Honeycomb's trace view for behavior. It's available now and built on.
|
By Honeycomb
Honeycomb and Embrace are extending the rigorous, data-driven practice that Honeycomb pioneered for foundational to mobile and web, giving, site reliability, and platform teams a complete, correlated picture of system health. The strategic partnership makes understanding performance and reliability for every user and every screen part of the observability practice, bringing new depth and standardization to how teams measure end user impact.
|
By Honeycomb
Honeycomb's Innovation Week: Observability for the Agent Era (May 12-14) For Day 1 of Innovation Week, Honeycomb co-founders Christine Yen and Charity Majors will share what it actually takes to understand and debug systems in the agent era, and what the best engineering teams are doing differently. A 3-Day Virtual Event for Teams Building the Future May 12: Get insights on how the best engineering teams are tackling the challenges of the agentic era.
|
By Honeycomb
Watch this video to see the re-imagined Canvas in action, where auto-investigation has already ranked your hypotheses before you open the tab, multiplayer agents build on each other's work in real time, and a custom skill encoding your team's own runbook can reprioritize the entire incident before you've had your morning coffee.
|
By Honeycomb
Watch this video to see Agent Timeline in action: one conversation ID, one view, every agent invocation, LLM call, tool call, and downstream trace, so you stop stitching tabs together and start finding the failure in seconds.
|
By Honeycomb
Honeycomb is an event-based observability tool, but you can-and should-use metrics alongside your events. Fortunately, Honeycomb can analyze both types of data at the same time. When maturing from metrics-based application monitoring to an observability-based development practice, there are considerations that can make the transformation easier for you and your team.
|
By Honeycomb
Evaluating observability tools can be a daunting task when you're unfamiliar with key considerations and possibilities. This guide steps through various capabilities for observability tooling and why they matter.
|
By Honeycomb
This document discusses the history, concept, goals, and approaches to achieving observability in today's software industry, with an eye to the future benefits and potential evolution of the software development practice as a whole.
- July 2026 (3)
- June 2026 (13)
- May 2026 (20)
- April 2026 (14)
- March 2026 (10)
- February 2026 (6)
- January 2026 (6)
- December 2025 (6)
- November 2025 (10)
- October 2025 (7)
- September 2025 (13)
- August 2025 (6)
- July 2025 (14)
- June 2025 (11)
- May 2025 (14)
- April 2025 (14)
- March 2025 (13)
- February 2025 (9)
- January 2025 (15)
- December 2024 (11)
- November 2024 (7)
- October 2024 (14)
- September 2024 (12)
- August 2024 (10)
- July 2024 (15)
- June 2024 (9)
- May 2024 (10)
- April 2024 (8)
- March 2024 (10)
- February 2024 (11)
- January 2024 (8)
- December 2023 (6)
- November 2023 (8)
- October 2023 (7)
- September 2023 (9)
- August 2023 (8)
- July 2023 (7)
- June 2023 (14)
- May 2023 (16)
- April 2023 (12)
- March 2023 (22)
- February 2023 (7)
- January 2023 (8)
- December 2022 (3)
- November 2022 (8)
- October 2022 (16)
- September 2022 (10)
- August 2022 (11)
- July 2022 (11)
- June 2022 (14)
- May 2022 (6)
- April 2022 (14)
- March 2022 (8)
- February 2022 (9)
- January 2022 (9)
- December 2021 (11)
- November 2021 (7)
- October 2021 (8)
- September 2021 (5)
- August 2021 (4)
- July 2021 (6)
- June 2021 (11)
- May 2021 (2)
- April 2021 (4)
- March 2021 (5)
- February 2021 (9)
- January 2021 (6)
- December 2020 (9)
- November 2020 (7)
- October 2020 (18)
- September 2020 (11)
- August 2020 (4)
- July 2020 (6)
- June 2020 (4)
- May 2020 (6)
- April 2020 (7)
- March 2020 (5)
- February 2020 (4)
- January 2020 (5)
- December 2019 (3)
- November 2019 (3)
- October 2019 (2)
- September 2019 (7)
- August 2019 (6)
- July 2019 (5)
- June 2019 (6)
- May 2019 (6)
- April 2019 (4)
- March 2019 (3)
- February 2019 (3)
- January 2019 (4)
- December 2018 (9)
- November 2018 (8)
- October 2018 (2)
- September 2018 (5)
- August 2018 (11)
- July 2018 (7)
- June 2018 (7)
- May 2018 (7)
- April 2018 (3)
Honeycomb is a tool for introspecting and interrogating your production systems. We can gather data from any source—from your clients (mobile, IoT, browsers), vendored software, or your own code. Single-node debugging tools miss crucial details in a world where infrastructure is dynamic and ephemeral. Honeycomb is a new type of tool, designed and evolved to meet the real needs of platforms, microservices, serverless apps, and complex systems.
Honeycomb provides full stack observability—designed for high cardinality data and collaborative problem solving, enabling engineers to deeply understand and debug production software together. Founded on the experience of debugging problems at the scale of millions of apps serving tens of millions of users, we empower every engineer to instrument and query the behavior of their system.