Observability  

Honeycomb and the Five Whys: Summary Post

By Charity Majors   |   October 8, 2016

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

Instrumentation   Observability  

Webinar Recap: How to Avoid Being On Call With Under-Instrumented Tools

"It's expensive. It's difficult. Our APM works just fine." The three myths of observability can lead to being on call with under-instrumented tools. That's exactly...

Logging   Observability  

Ingesting HTTP Access Logs from AppService

Debugging application performance in Azure AppService is something that’s quite difficult using Azure’s built-in services (like Application Insights). Among some of the issues are visualizations,...

Observability  

Honeycomb Supports Service Ownership

The software industry is moving toward teams that own the services they build. This concept encloses principles and possibilities from movements toward microservices, DevOps, Agile,...