Honeycomb

San Francisco, CA, USA
2016
  |  By Fred Hebert
One of the main pieces of advice about Service Level Objectives (SLOs) is that they should focus on the user experience. Invariably, this leads to people further down the stack asking, “But how do I make my work fit the users?”—to which the answer is to redefine what we mean by “user.” In the end, a user is anyone who uses whatever it is you’re measuring.
  |  By Ken Rimple
Are you attempting to connect Honeycomb to a standalone (not hosted with Vercel) Next.js application? Most of the Next.js OpenTelemetry samples in the wild show how to connect Next.js to Vercel’s observability solution when hosting on their platform. But what if you’re hosting your own standalone Next.js server on Node.js? This blog post will get you started ingesting your Next.js application’s telemetry into Honeycomb.
  |  By Nick Travaglini
Here at Honeycomb, we emphasize that organizations are sociotechnical systems. At a high level, that means that “wet-brained” people and the stuff they do is irreducible to “dry-brained” computations. That cashes out as the inability to ultimately remove or replace people in organizations with computers, in spite of what artificial general intelligence (AGI) ideologues would have you believe.
  |  By Martin Thwaites
With more and more people adopting OpenTelemetry and specifically using the tracing signal, I’ve seen an uptick in people wanting to add the entire request and response body as an attribute. This isn’t ideal, as it wasn’t when people were logging the body as text logs. In this blog post, I’ll explain why this is a bad idea, what are the pitfalls, and more importantly, what you should do instead.
  |  By Rox Williams
88% of online consumers are less likely to return to a site after a bad user experience. This means that addressing frontend issues such as slow load times, broken features, and unresponsive elements is crucial. Frontend monitoring helps development and IT teams proactively catch and resolve these issues to improve their user experience.
  |  By Erwin van der Koogh
One of the hardest parts of my job is to get people to appreciate just how much of a difference Honeycomb/observability 2.0 is compared to their current way of working. It’s not just a small step up or a linear improvement. Rather, it’s an entire step change in the way that you write, deploy, and operate software for your customers.
  |  By Brian Chang
Since its early startup beginnings in Amsterdam, Booking.com has redefined the travel industry, establishing itself as a premier platform for millions of travelers worldwide. With over 28 million accommodation listings and a staggering 1.5 million room nights booked every day, Booking.com operates on a scale that demands a robust and constantly monitored infrastructure.
  |  By Brian Chang
For years, Fender Musical Instruments has been synonymous with iconic guitars and amplifiers. But in recent years, the company has expanded its legacy into the digital realm, offering tools like Fender Play, an innovative learning platform for aspiring musicians. Behind this digital evolution lies a focus on delivering exceptional user experiences for its consumer-facing applications—a mission supported by Honeycomb for Frontend Observability.
  |  By Fred Hebert
Back in Alerts Are Fundamentally Messy, I made the point that the events we monitor are often fuzzy and uncertain. To make a distinction between what is valid or invalid as an event, context is needed, and since context doesn’t tend to exist within a metric, humans go around and validate alerts to add it. As such, humans are part of the alerting loop, and alerts can be framed as devices used to redirect our attention. In this post, I want to drive this concept a bit further.
  |  By Hannah Henderson
There are a limited number of investments that a team can make in any given year and it can be daunting to choose the “right” ones. In R&D, there is always more to do. There is always more to research, design, build, fix, maintain, and improve. Spread across multiple domains, the possibilities multiply: we’re spoiled for choice—and, while inspiring, the breadth of possible investment areas can be overwhelming.
  |  By Honeycomb
As a software developer, how is observability relevant to me? What is this OpenTelemetry thing? Austin Parker gives a great overview.
  |  By Honeycomb
Charity breaks down the progress in Observability in recent years: there's a sea change underway. This is not an incremental improvement, but a radical shift in how we understand the software we build.
  |  By Honeycomb
Charity Majors brought the word "observability" into software. Now she describes the one major shift that we need to get more out of observability at lower cost.
  |  By Honeycomb
What do you do when OpenTelemetry is sending way more telemetry than you expect? Jessitron walks you through 2 quick ways to check where all that data is coming from.
  |  By Honeycomb
In this 3-minute preview of our Director's Guide to Observability.
  |  By Honeycomb
Liz Fong-Jones walks you through how we debugged our Kubernetes Autoscaler with Honeycomb Log Analytics to achieve cost savings with Graviton4 instances. Having great observability is one way Honeycomb saves money.
  |  By Honeycomb
In this installment of Ask the Experts, Anijah asks Zach McCoy about distributed and what problems it solves.
  |  By Honeycomb
When an alert goes off because a Service Level Objective (SLO) is in danger of violation, it comes with a lot of context about what has been going wrong and for how long. Then Honeycomb gives you tools to explore the where & why. Here, Martin Thwaites walks through an example of diagnosing slower performance. What service is the problem, and under what circumstances?
  |  By Honeycomb
In this episode, Audrey Herndon, Technical Customer Success Manager at Honeycomb, asks #observability expert Dan Ravenstone at Top Hat, about the all-in-one solution.
  |  By Honeycomb
In this episode, Victoria Perera Roman, Sr. Technical Customer Success Manager at Honeycomb, asks #observability expert Chris Bertinato, Systems Architect at NS1, why some companies resist adopting Honeycomb.
  |  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.