Infographic 2020 Observability Maturity Survey Results
5 minute read
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.
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.
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.