Developers code a median of 52 minutes per day — or about 4 hours and 21 minutes during a typical work week from Monday to Friday. This article discusses how measuring DevOps metrics and making the flow of work visible helps teams eliminate bottlenecks and gives developers more time to code.
More and more developers have got involved in how to use observability. This has led to a thriving community of developers that have created and supported open source projects around that data. What will happen next around observability? This article takes a look at predictions for the coming year.
Getting data from Continuous Integration (CI) and Continuous Deployment (CD) and then making it useful to the whole business in the same way has been more difficult. Using a Monitoring as Code approach can help. Find out what makes Monitoring as Code different.
Erez Berkner, the co-founder and CEO of Lumigo, spoke with JAXenter about the cloud observability space, elaborating on what it’s trying to solve and how it’s different from monitoring. He explains in detail how Lumigo helps make sense of the ever-growing complexity of cloud-native applications and allows developers to find the root cause of an issue in highly-distributed systems. Erez explains Lumigo’s decision to expand to Kubernetes and hybrid apps and reveals the company’s plans for further down the road.
Gartner has predicted more than 75 percent of global organizations will be running containerised applications in production by 2022. With so many more moving parts to look at, developers have to automate how they gather data on their infrastructure components, while security teams have to understand the new models for applications too.
We spoke with Stela Udovicic, Product Marketing Director at VMware Tanzu about the State of Observability Report 2021. Stela discusses increasing cloud complexity and its drawbacks, what observability red flags to watch out for, predictions for 2022, and more.
Observability can be used to improve how we think about our roles within companies. At the same time, linking observability to a business goal can be an effective way to ensure that other teams and departments care about the data involved. See what developers should know about observability.
From the starting point of system reliability or business objectives, we can make a better case around how observability data can improve software development over time. What are we doing today and how can we do better?
Understanding what observability is – and equally what it is not – is essential for anyone involved in the wider software engineering sector. Observability has its roots in engineering and control theory such as papers published in the 1960s by Rudolf Kalman.
As deep systems become more prevalent in today’s high-speed digital enterprises, DevOps must find the best tools in order to manage them. We spoke with Ben Sigelman, co-founder and CEO at LightStep, about how deep systems emerge, microservice observability, and the difficult aspects of dealing with deep systems.
Let’s clear the mists from observability. Observability is finding out why something is broken, determining the impact of that break, and assessing if the changes we think will fix the problem actually will and do fix that problem. In this article, Cory Watson discusses the three pillars of observability, where to start, and what it can do to change not only your IT incidents but also your work culture.
