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.
SLOs: Uniting Engineering and Business Teams Behind Common Goals
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.
The Open Source Observability Landscape
These days, there’s an observability tool around every corner. We get it – it’s confusing! How do you make sense of all these tools, and how do they stack up when it comes to solving problems quickly?
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.
Developing a Culture of Observability
Observability gives engineers insight into how their systems function and how users experience the resulting services; it allows you to answer questions that you didn't anticipate having to ask.
Even then, asking questions is only half of the battle. Having the tools to explore and investigate issues in your code doesn’t necessarily mean you have a culture that supports and drives the greater benefits of observability: happier engineers, happier customers, and a stronger business overall.
The Path from Unstructured Logs to Observability
If you’re trying to achieve observability starting with unstructured logs, you’ve got some work ahead of you. Logs are no longer human scale.
When your only view of the system is through the instrumentation of your code, how it outputs what it tells you is as critical as what it outputs. Discover the best path from where you are today to a future of observability with this guide.
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.
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.
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?
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.
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.
Distributed Tracing – A Guide for Microservices and More
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? Distributed Tracing – A Guide for Microservices and More is for you. 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.
Always Bee Tracing
At Honeycomb, we practice observability to know how our production systems are behaving in real-time. Distributed tracing is just one feature we use to solve issues fast and see what’s happening across all services. With tracing inside Honeycomb, we switch easily to different chart views – histograms, heat-maps and waterfall trace views.
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.