Honeycomb

San Francisco, CA, USA
2016
  |  By Brian Chang
Since its inception in 2004, Lansweeper has been at the forefront of helping businesses understand, manage, and protect their IT devices and networks through a powerful IT asset management platform. As the platform grew from an on-premises solution to a cloud-based SaaS offering, Lansweeper expanded its reach to a global, multi-region customer base.
  |  By Jessica Kerr
Observability means you know what’s happening in your software systems, because they tell you. They tell you with telemetry: data emitted just for the people developing and operating the software. You already have telemetry–every log is a data point about something that happened. Structured logs or trace spans are even better, containing many pieces of data correlated in the same record. But you want to start from what you have, then improve it as you improve the software.
  |  By Nick Travaglini
As discussed in the first article in this series, a Center of Production Excellence (CoPE) is a more or less formal, provisional subsystem within an organization. Its purpose is to act from within to change that organization so that it’s more capable of achieving production excellence. The series has, to date, focused mainly on how best to construct such a subsystem and what activities it should pursue.
  |  By Liz Fong-Jones
Let’s be real, we’ve never been huge fans of conventional unstructured logs at Honeycomb. From the very start, we’ve emitted from our own codestructured wide events and distributed traces with well-formed schemas. Fortunately (because it avoids reinventing the wheel) and unfortunately (because it doesn’t adhere to our standards for observability) for us, not all the software we run is written by us.
  |  By Mei Luo
At Honeycomb, we know how important it is for organizations to have a unified observability platform. This is why we’re launching Honeycomb Telemetry Pipeline and Honeycomb for Log Analytics: to enable engineering teams to send and analyze data—including logs—into a single, unified platform. For too long, teams have had to wrangle large volumes of logs, their context scattered across multiple teams and tools, leading to knowledge silos.
  |  By Elsie Phillips
Over the past six weeks, we introduced a series of impactful updates aimed at making your observability workflows faster, more unified, and more collaborative. Here’s a snapshot of what we worked on.
  |  By Elsie Phillips
Frontend development has evolved rapidly over the past decade, but one challenge remains constant: understanding what’s happening in real-time across diverse browsers, environments, and user interactions. This is where observability steps in—but how does it apply to the frontend world where user experience can break in countless, unexpected ways?
  |  By Fahim Zaman
Real user monitoring (RUM) began as a straightforward approach to tracking basic web performance metrics. Focused on things like page load times and response rates, RUM relied on server-side logging and simple browser timings. While these tools captured Core Web Vitals (CWVs), they offered limited insights into how users actually interacted with pages, focused mainly on server-side performance.
  |  By Jessica Kerr
Hint: Append them to your structured logs or spans.
  |  By Winston Hearn
Recently, we announced the launch of Honeycomb for Frontend Observability, our new solution that helps frontend developers move from traditional monitoring to observability. What this means in practice is that frontend developers are no longer limited to a metrics view of their app that can only be disaggregated in a few dimensions. Now, they can enjoy the full power of observability, where their app collects a broad set of data as traces to enable much richer analysis of the state of a web service.
  |  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
In this episode of Ask the Experts, Victoria Perera Roman, Sr. Technical Customer Success Manager at Honeycomb, asks Dominic Marino, Principal #software #engineer at Cargurus and #observability expert, why some companies resist adopting Honeycomb.
  |  By Honeycomb
There's a new way to flip through your data in Honeycomb, released this week! It's super for looking at structured logs. It's called: Explore Data. Get directly at the logs, spans, events, or metrics that power the fast analysis you can do with Honeycomb. See all the fields, the whole variety of values — now ordered by timestamp, with pagination. Modify your query and graphs right from the data table. It's all connected!
  |  By Honeycomb
See how Honeycomb gives you quick insight into web site performance, including Honeycomb gives you the metrics you need to see, and all the context you need to improve them.
  |  By Honeycomb
Martin investigates: what database queries are taking the longest? Then he digs into the one taking the most time, and asks: What user-initiated requests trigger this query? This kind of question helps developers focus our efforts where they count. And it's possible in Honeycomb with Relational Fields. This is #observability during development, using #OpenTelemetry #tracing and Honeycomb.
  |  By Honeycomb
In this quick tutorial video, Jessitron walks you through what to do if you create a #query in Honeycomb in the wrong environment. Chapters.
  |  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.