Honeycomb

San Francisco, CA, USA
2016
  |  By Rox Williams
Birdie wanted to uplevel observability to a platform that would provide meaningful insights for application performance and debugging. Ensuring customers can provide seamless and timely care to in-home patients stands as a top priority for Birdie, and the development team takes pride in building and maintaining a high-quality platform distinguished by its reliability and responsiveness.
  |  By Phillip Carter
This post first appeared on Phillip's personal blog. Back in May 2023, I helped launch my first bona fide feature that uses LLMs in production. It was difficult in lots of different ways, but one thing I didn’t elaborate on in several blog posts was how lucky I was to have a coherent way to get the data I needed to make the feature useful for users.
  |  By Jason Harley
We're delighted to introduce our new Ingest API Keys, a significant step toward enabling all Honeycomb customers to manage their observability complexity simply, efficiently, and securely. Ingest Keys are currently available for Environment & Services customers, with Classic support and programmatic key management capabilities under development and coming soon!
  |  By Austin Parker
In today’s economic and regulatory environment, data sovereignty is increasingly top of mind for observability teams. The rules and regulations surrounding telemetry data can often be challenging to interpret, leaving many teams in the dark about what kind of data they can capture, how long it can be stored, and where it has to reside. In the past, addressing these issues at scale was a costly endeavor.
  |  By Jessica Kerr
“Mommy, where does software come from?” “Software grows in a circle, just like this!” The software development lifecycle (SDLC) is always drawn as a circle. In many places I’ve worked, there’s no discernable connection between “5. Operate” and “1. Plan.” However, at Honeycomb, there is. More on that later.
  |  By Mike Terhar
When you have questions about your software, telemetry data is there for you. Over time, you make friends with your data, learning what queries take you right to the error you want to see, and what graphs reassure you that your software is serving users well. You build up alerts based on those errors. You set business goals as SLOs around those graphs.
  |  By Rox Williams
At Honeycomb, we are very concerned about privacy and data sovereignty—it’s something we take very seriously, and in an effort to serve our customers better, we’re thrilled to announce that we now offer data residency in Europe. This new instance will allow Honeycomb customers to store their data in the US, in Europe, or both. Let’s talk about the details.
  |  By Charity Majors
The cost of services is on everybody’s mind right now, with interest rates rising, economic growth slowing, and organizational budgets increasingly feeling the pinch. But I hear a special edge in people’s voices when it comes to their observability bill, and I don’t think it’s just about the cost of goods sold.
  |  By Fred Hebert
Good alerting hygiene consists of a few components: chasing down alert conditions, reflecting on incidents, and thinking of what makes a signal good or bad. The hope is that we can get our alerts to the stage where they will page us when they should, and they won’t when they shouldn’t. However, the reality of alerting in a socio-technical system must cater not only to the mess around the signal, but also to the longer term interpretation of alerts by people and automation acting on them.
  |  By Jeremy Blythe
There’s plenty of literature on the mechanics of instrumenting code with OpenTelemetry and delivering it to Honeycomb. However, I’ve not found many guides on the craft of instrumenting code in order to have a good observability experience in your system. A lot of focus is placed on automatic instrumentation—which is great, particularly if you’re new to observability or retrofitting—but it misses the power of good instrumentation at the application level.
  |  By Honeycomb
Imagine a universe in which a massively multiplayer online role-playing game (MMORPG) sets Guinness World Records for the size of its online space battles—and that game is built on 20-year-old code. Well, imagine no more. Welcome to the world of EVE Online, where hundreds of thousands of players interact across 7,800+ star systems and participate in more than one million daily market transactions. As you might guess, updating and maintaining this codebase without interrupting game play could pose quite a challenge.
  |  By Honeycomb
Honeycomb Customer Success Manager Josh Levin explains how to troubleshoot production incidents using Honeycomb's telemetry data: metrics, traces, and logs. While these data forms have separate interfaces, you can investigate seamlessly within Honeycomb. Josh highlights the key role of the "retriever" service in data ingestion and querying and demonstrates cross-validating tracing data with metrics to spot anomalies in pod deployments and resource usage, presented in a separate dataset. He also uses effective log filtering and searching for keywords like "update status.".
  |  By Honeycomb
Buildevents is a small binary used to help instrument builds to generate trace telemetry. It populates the trace with metadata from the GitHub Actions environment so you have details about what occurred throughout the entire build. In this tutorial, learn how to instrument with Buildevents and GitHub actions.
  |  By Honeycomb
Buildevents is a small binary used to help instrument builds to generate trace telemetry. It populates the trace with metadata from the GitHub Actions environment so you have details about what occurred throughout the entire build. In this tutorial, learn how to instrument with Buildevents and GitHub actions.
  |  By Honeycomb
Nathan Lincoln, an SRE at Honeycomb, walks through the basics of feature flag best practices (using LaunchDarkly) to help you maintain a stable system. Feature flags are useful for reducing outages and downtime in our systems by allowing traffic segmentation, but they can create chaos without proper maintenance.
  |  By Honeycomb
Tech debt. Vendor redundancy. System fragmentation. Startups and cloud–born companies are looking at vendors for cost-cutting opportunities. But how do you balance vendor costs and value when those resources and tools bring efficiencies as high as the monthly bills? In this session, Charity Majors and Gergely Orosz share advice on managing spend in a vendor-dependent world.
  |  By Honeycomb
Hear from Odyssey Interactive to learn how they implemented Honeycomb to accelerate development time and resolve issues quickly.
  |  By Honeycomb
Honeycomb's trace-aware proxy, Refinery, allows you to sample your data to reduce costs while giving you the ability to ensure the lowest margin of error on your most important data.
  |  By Honeycomb
Stepping through a trace is an invaluable debugging workflow, providing a way to follow requests from service to service even as the applications we manage become more complex and distributed. That same complexity can make getting started with distributed tracing feel overwhelming, but it’s important to remember that instrumenting your code is an additive process—you don’t need to boil the ocean. A trace through a thousand services starts with a single ID.
  |  By Honeycomb
Chris Bertinato, Software Architect at NS1, and Nate Daly, Head of Architecture at NS1 along with Jessica Kerr, Honeycomb Developer Advocate, and Account Executive Scott Phillips discuss how NS1 used distributed tracing to scale their organization and accelerate their migration from a monolith to microservices.
  |  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.

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.