June 16, 2021
Observability Maturity Community Research Findings 2021
Our report takes a look at the observability landscape and how practices are evolving. Learn where your organization is on the observability maturity spectrum and see how organizations on the higher end of the spectrum are realizing the benefits.
October 5, 2020
Infographic 2020 Observability Maturity Survey Results
Research findings show a strong link between observability capabilities and production excellence. We found that advanced observability tooling and practices go hand-in-hand with achieving better outcomes for engineering teams, the services they provide, and the customers who use their products.
April 6, 2020
Observability Maturity Community Research Findings
Adopting observability tools, site reliability engineering (SRE) practices, and a culture of shared ownership translates to efficiencies across the software engineering cycle. Industry survey results are in! We learned that advanced observability tooling and practices go hand-in-hand with achieving better outcomes: Advanced teams realize better outcomes and possess the confidence to solve problems when crisis strikes—52% are very confident in their capacity to detect bugs in production and another 40% are somewhat confident. Read results & learn why o11y maturity drives production excellence.
February 10, 2020
SLOs: Uniting Engineering and Business Teams Behind Common Goals
A 451 Research | Business Impact Brief: If an app/service performs poorly, how likely are you to switch to a different brand? Turns out 79% claim very or somewhat likely. SLOs are now a best practice approach to help engineers and business stakeholders understand what to measure about their service for a consistent quality customer experience.
June 10, 2019
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.
June 4, 2019
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.
May 8, 2019
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.
February 1, 2020
The Open Source Observability Landscape
With this guide, we take a closer look at the most popular open-source approaches for storing and accessing app telemetry. We dive into Prometheus, ELK, and Jaeger to celebrate their growing popularity, what they bring to the table, and how they work in tandem with Honeycomb.
March 25, 2019
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?
March 4, 2019
Getting Started with Honeycomb Metrics
You can use metrics and events in the same interface for observability. This whitepaper shows you how to get metrics into Honeycomb, which ones to send, and how to analyze them along with your events.
February 13, 2019
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.