White papers and guides

Framework for an Observability Maturity Model

Everyone is talking about "observability", but many don’t know what it is, what it’s for, or what benefits it offers. The framework we describe here is a starting point. With it, we aim to give organizations the structure and tools to begin asking questions of themselves, and the context to interpret and describe their own situation--both where they are now, and where they could be. 

Building Your Observability Practice with Tools that Co-exist

Honeycomb's goal is to augment and expand your ability to deliver  your service and improve your bottom line, not require you to rip out the tooling your organization has depended on up to now. You can benefit from using  Honeycomb alongside what’s been working for you until now. 

Calculating Costs for Observability

Debugging in production is a requirement for modern teams, especially for teams who ship frequently. DevOps teams need the best tools to debug issues when they come up, not just hope they can catch everything in staging. You need to make the move to next-gen APM--but how much will it cost? How much should it cost?

The New Rules of Sampling

It is not feasible to run an observability infrastructure that is the same size as your production infrastructure. Past a certain scale, the cost to collect, process, and save every log entry, every event, and every trace that your systems generate dramatically outweighs the benefits. The question is, how to scale back the flood of data without losing the crucial information your engineering team needs to troubleshoot and understand your system's production behaviors? Sampling is the key.

Why Your Business Needs Observability

“…the average developer spends more than 17 hours a week dealing with maintenance issues, such as debugging and refactoring. In addition, they spend approximately four hours a week on “bad code,” which equates to nearly $85 billion worldwide in opportunity cost lost annually.”
-Stripe's 2018 "Developer Coefficient" survey report

Find out how observability can help.

Distributed Tracing – A Guide for Microservices and More

Want to know what tracing is, what it's for, and how to get the power that it offers to debug and explore your code in production? Distributed Tracing – A Guide for Microservices and More is for you. The 3rd volume in the Honeycomb Observability e-Guide Series, this guide covers an introduction to the topic of tracing, its history, how to think about tracing, and how to add traces to your instrumentation.

Guide: Observability for Developers

This guide provides the means to measure your current level of observability practice and how to get to the next level. It goes into detail about not just why, but how you can implement observability as an integral part of your development process and culture.

Guide: Achieving Observability

This guide 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.

Always Bee Tracing

At Honeycomb, we practice observability to know how our production systems are behaving in real-time. Distributed tracing is just one feature we use to solve issues fast and see what’s happening across all services. With tracing inside Honeycomb, we switch easily to different chart views – histograms, heat-maps and waterfall trace views.

o11ycon 2018 - Discussion Findings

At the first-ever observability conference, attendees broke out into various groups to have open space-style discussions (OSSD) on various sub-themes in observability. This document summarizes those lightning talks presenting our OSSD Sessions - carving out what our industry means when we talk about observability.