Better failure measurements, so you can quickly see where to improve

One of the hardest things to figure out when tracking your DORA metrics is your team's change failure rate and MTTR. With our recent improvements to how we measure and display failure you can now see, at a glance, how long a deploy has spent in a failure state and exactly what caused it.

Throughout Sleuth we now represent a deploy's health as a circle, displaying the amount of time it has spent in each health state. Furthermore, the deploy Impact tab has been updated to show exactly when and why a deploy transitioned from one health to another.

With these updates it's now that much easier to understand how to improve your team's failure rate and MTTR and make your way to faster and safer deploys!

100% accurate metrics setup in 2 minutes or less with CI/CD auto detected deploys

You can now setup Sleuth for 100% accurate metrics without any modifications to your deployment process or scripts by connecting to your CI/CD provider

Just connect Sleuth to your CI/CD (via OAuth or API key), map your Sleuth Environments to the build/job that deploys for you and sit back and watch your metrics come to life!

Behind the scenes Sleuth is monitoring your CD builds and when we find a new one we do our magic to generate your DORA metrics for every deploy.

Sleuth already supports integrations with most common CI/CD tools (GitHub actions, Jenkins, CircleCI and more) and we are building out more everyday. If we don’t yet support your CI/CD provider we’d love to hear from you at But remember, you can still always fall back to 100% accurate metrics by setting up a webhook which works for any deployment process you’ve put in place.

Track your failure rate and MTTR your way

One of Sleuth's most popular ways to track change failure rate and MTTR is by tracking your teams incidents. We have a number of wonderful first-class integrations. However, many teams have a home-grown or manual process.

For all of you, Sleuth now supports Custom Incident tracking! Just create a custom incident impact source and hit Sleuth's REST API at the start and end of an incident and Sleuth will do the rest, surfacing your blended change failure rate and MTTR.

Propel your change failure rate and MTTR with CI/CD builds

As of today you can use any CI/CD build to track your change failure rate and MTTR.

Change failure and the sources that propel it differ wildly from team to team. That's why here at Sleuth we feel it's imperative to support all sources of failure your team already relies on. 

Many teams run CI/CD builds that can spot failure before it hits their customers. And others run CI/CD smoke test builds against their running Environments.

Just connect any of our supported CI/CD integrations like Jenkins, Github Actions (and more) and you'll be tracking change failure and MTTR in minutes!

GitLab CI/CD Pipelines integration

We love GitLab here at Sleuth and we can tell you that a good portion of our users to do too! Sleuth has supported GitLab for code and issues for over a year. 

Now you can integrate Sleuth with GitLab to connect your builds to your deploys as well.

If your team is using GitLab for CI/CD or test builds, just head on over the integrations page, enable GitLab and start seeing your builds in Sleuth today!

Show Previous EntriesShow Previous Entries