Observability  

Honeycomb and the Five Whys: Summary Post

By Charity Majors  |   Last modified on April 18, 2022

Anchor post at the top of this week’s long series of “vision” posts, so everything doesn’t just appear backwards. :)

This week we set forth the case for why Honeycomb is the future. We’ve seen the future, we’ve built massive cotenancy platforms, we’ve now built the observability product we never ever want to live without again as users.

And we want to be the first thing you think of when you’re yanking your infra into the future, too. Or when you have tough problems with your visibility into your databases and storage tiers, or unexplained behavior to debug, or you just really want to make it easier for your teams to collaborate and gain more systems-y skills.

In order, here are links to the posts:

Five ways this matters.

In the next five (short!) posts I will lay out what is unique about Honeycomb, the problems it solves, and the tradeoffs we’ve had to make to fulfill our promises. Those five sections are:

Cheers. We look forward to seeing your data flow. :)

~ The Honeys

 

Related Posts

Observability  

Iterating Our Way Toward a Service Map

For a long time at Honeycomb, we envisioned using the tracing data you send us to generate a service map. If you’re unfamiliar, a service...

Observability   Teams & Collaboration  

Autocatalytic Adoption: Harnessing Patterns to Promote Honeycomb in Your Organization

When an organization signs up for Honeycomb at the Enterprise account level, part of their support package is an assigned Technical Customer Success Manager. As...

Logging   Observability  

Surface and Confirm Buggy Patterns in Your Logs Without Slow Search

Incidents happen. What matters is how they’re handled. Most organizations have a strategy in place that starts with log searches—and logs/log searching are great, but...