Sleuth

How to define software failure

Two of the four DORA metrics, Change Failure Rate and MTTR, require that you first define what failure means. Does failure always mean incident? Or should failure mean rollback? In this video, Don walks you through a couple different ways to define failure, and how Sleuth does it today. SLEUTH A deploy-based DORA / Accelerate Metrics tracker both managers and developers love.

The wrong lessons to learn from the Log4j vulnerability

Log4j and Java sucks, but I don't use that, so I'm safe...right? Wrong. This video walks through the wrong lessons to take away from the huge Log4j remote code execution vulnerability, and points you at the lessons you should be learning instead. While the Log4j vulnerability may not directly affect you, its type of vulnerabilities certainly do.

How to easily track DORA metrics

With Sleuth, you can instantly and automatically track the four DORA metrics: Change Lead Time, Deploy Frequency, Change Failure Rate, and MTTR. No more, no less. Sleuth tracks them accurately, doesn't attempt to track dubious individual metrics, and doesn't require any manual work. SLEUTH A deploy-based Accelerate Metrics tracker both managers and developers love.

How to Reduce Change Lead Time

The time it takes to get a change into production, also known as Change Lead Time, is an important measure of developer productivity, and one of the four DORA metrics. In Sleuth, you can easily break down Change Lead Time into activities to get insights into potential bottlenecks. SLEUTH A deploy-based Accelerate Metrics tracker both managers and developers love.