DevOps and observability in the 2020s
What do the data tell us on the direction modern software development is going? Cloud, open source, machine learning — it’s all here, but blind spots remain.
DevOps Pulse is an annual analysis of the DevOps industry, conducted by logz.io. Findings from the 2019 version have just been published, and we take the opportunity to share and comment on them with Tomer Levy, logz.io CEO. Levy co-founded logz.io in 2014 and has managed to raise about $100 million and build a team of 250 people to date, on the premise of offering an open-source based solution for log management.
The 2019 survey focuses on observability, bringing DevOps engineers’ insights into what it means to make systems observable, how to achieve that outcome, and how observability contributes to maximizing product performance. It may well give a glimpse into the future of software development in the 2020s. First software development merged with operations, giving us DevOps. Then DevOps became data-driven. What’s next?
Logz.io press release highlights the growing popularity of observability, the strategic role it plays in DevOps processes, and the challenges preventing teams from achieving full observability into their systems. With about 1000 people taking the survey, the majority of whom were not logz.io customers, it should be reasonably close to being representative of the industry.
What’s piqued our interest to boot was the diversity of (self-identified) roles of the people who took the survey. From managers and directors to developers, DevOps engineers, and system administrators. Last time we checked, boundaries and responsibility split between some of those roles did not seem exactly clear. Looks like this is still the case.