DevOps Pulse 2022: Production Issues Take Longer to Solve Despite Advancements in Observability

Fifth Annual Reports Shows Cloud & Observability Efforts Advancing Against Backdrop of Higher Response Times and Microservices Complexity Challenges

BOSTON & TEL AVIV, Israel--()--Logz.io, a leading open source observability platform for modern DevOps and security teams, today released their fifth annual DevOps Pulse 2022 Report, which analyzes key trends, points of interest, and challenges experienced by developers every day.

Alongside the growing advancement of observability practices, the 2022 DevOps Pulse survey identifies issues related specifically to the monitoring of complex microservices and mean time to recovery (MTTR). The report combines data from observation and consumer insights of 1,000 engineers.

DevOps Pulse 2022 respondents consistently reported increasing complexity across their cloud environments – driven by everything from expanding microservices architecture to the proliferation and complexity of observability tools themselves – meaning they are struggling to maintain clear visibility, quickly resolve production issues and manage related monitoring costs.

One of the most interesting, yet troubling, findings of the report is that despite all of the advancement and maturity of observability systems, production issues take longer to resolve. Sixty four percent of respondents reported an average MTTR of over an hour compared to 47% reported in the DevOps Pulse 2021. What's more, 53.4% of respondents surveyed last year claimed to have resolved production issues within an hour on average – this year, that number dropped to 35.94%. This trend is being driven by factors ranging from growing cloud data volumes and systems complexity, to issues of observability tool sprawl, and the need for greater expertise among DevOps teams.

Additional key findings identified in the report include:

  • Observability costs and data volumes are growing concerns: With 27% of respondents ranking total cost of ownership and the large volumes of data being ingested into the tools among their main challenges in maintaining effective observability.
  • Observability is maturing. Some 77% of respondents rated their efforts over three on a scale of 1-5 when asked to indicate how extensive and mature their observability strategy has become – compared to last year, when more than 30% of respondents indicated a low score of two or less.
    • This is combined with a palpable increase in observability tool sprawl. Twenty two percent of those surveyed indicated their organization uses five or more observability tools, compared to 11% last year.
  • Open source capabilities are widely used by 90% of respondents. Open Source observability is the most common way to deploy observability.
  • A shared services model is growing in popularity: Over 85% of respondents indicated that their organizations operate using a shared services observability model in which a central team is responsible for implementing and maintaining tooling for other stakeholders such as app developers, SREs and DevOps teams.
  • Data security has moved to the forefront of DevOps teams’ priorities: ranking at fourth overall (33%) as one of the survey’s primary observability challenges. Statistics in the report related to security further contextualize the central role that security oversight plays across the industry.

“Essentially, the 2022 DevOps Pulse Report reveals that there is too much data and the current model for observability is broken,” says Tomer Levy, Chief Executive Officer of Logz.io. “As practices and implementations expand, organizations are becoming more concerned about the impact of data volumes on production quality and cost. In addition to offering an analysis of the evolving landscape, DevOps Pulse 2022 calls on organizations to think carefully about the impact of Kubernetes and Microservices and constantly evaluate telemetry data value and hygiene.”

By closely tracking and analyzing data that is central to core observability requirements and finding ways to reduce MTTR despite identified challenges, organizations can better calculate associated spending and ROI. Emphasizing these factors combined with an increased focus on application and data security solve the challenges identified by DevOps teams and observability practitioners.

For more information on Logz.io’s 2022 DevOps Pulse Report, visit https://logz.io/gap/devops-pulse-2022/.

About Logz.io

Logz.io is a leading cloud-native observability platform that enables engineers to use the best open source tools in the market without the complexity of operating, managing, and scaling them. Logz.io offers four products: Log Management built on ELK, Infrastructure Monitoring based on Prometheus, Distributed Tracing based on Jaeger, and an ELK-based Cloud SIEM. These are offered as fully managed, integrated cloud services designed to help engineers monitor, troubleshoot and secure their distributed cloud workloads more effectively. Engineering driven companies like Siemens, Unity and ZipRecruiter use Logz.io to simplify monitoring and security workflows, increasing developer productivity, reducing time to resolve issues, and increasing the performance and security of their mission-critical applications.

Contacts

Franki Darnold
logz@walkersands.com

Release Summary

Logz.io, a leading open source observability platform for modern DevOps and security teams, releases their fifth annual DevOps Pulse 2022 Report.

Contacts

Franki Darnold
logz@walkersands.com