White papers and guides

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.

Tracing and Observability: This Must Be The Trace

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? This Must Be The Trace. 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.

Honeycomb.io Datasheet

Honeycomb is the most powerful product on the market for visualizing, understanding, and debugging distributed software.

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.