RESULTS
Observability gets results
We surveyed ITOps and developer teams worldwide to identify the qualities of leading organizations — then measured the outcomes of their observability efforts:
- 2.9 times better visibility into application performance
- 2.3 times better visibility into security posture
- Almost 2 times better visibility into public cloud infrastructure
LEADERSHIP
Attributes of observability leaders
Observability leaders share four key factors of success. Only 11% measured up; 29% were intermediate (three factors), and 60% were beginners (0-2 factors). The factors:
- Experience: Length of time maintaining an observability practice
- Data correlation: Extensive ability to correlate data across IT systems
- Vendor rationalization: Progress from scattershot tooling toward a platform approach
- AI/ML: Use of artificial intelligence/machine learning within observability tools
OBSTACLES
Key challenges
Respondents identified the greatest problems they face in evolving strong observability practices, including technology, infrastructure, culture and internal support.
- Asked to name their No. 1 problem, technology (41%) led infrastructure complexity (25%), culture (18%) and internal support (10%).
- 53% say they only use cloud providers’ native tools — limiting visibility in a hybrid, multicloud world.
- Developers admit they don’t use observability tools nearly as much as ops teams think they do.
TAKEAWAYS
How to be a leader
Observability excellence is foundational to success for modern organizations. The report outlines how to up your game, including:
- Prioritizing the biggest challenge: data collection and correlation.
- Rationalizing your vendor list: Commit to broad reach, deep insights and extreme flexibility.
- Trusting the algorithms: AI/ML and automation help achieve scale and velocity.
- Doubling down on DevOps: Roles, processes and culture matter.
