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

OpenTelemetry   Observability  

What Is a Telemetry Pipeline?

In a simple deployment, an application will emit spans, metrics, and logs which will be sent to api.honeycomb.io and show up in charts. This works...

Software Engineering   Observability  

5 Ways Honeycomb Saves Time, Money, and Sanity

If debugging has sucked the soul out of your engineers, we’ve got the answer: event-based observability. Instead of spending hours and resources trying to find...

Observability  

Our Favorite #chArt

Heatmaps are a beautiful thing. So are charts. Even better is that sometimes, they end up producing unintentional—or intentional, in the case of our happy...