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!

Drive your change failure rate and MTTR with Incidents via FireHydrant

Many teams define change failure as when they've caused an incident. Their MTTR is how long it takes the team to recover. 

Sleuth now integrates with incident management platforms to automatically incorporate your Incidents into your change failure rate and MTTR. Our first integration is with the fine folks over at FireHydrant.

It only takes a minute to connect and you'll see your Accelerate (DORA) metrics reflect your data straight away.

If you're using PagerDuty, Statuspage or Blameless to manage incidents, never fear, we'll have you covered over the next few weeks!

Discover change lead time bottlenecks

Sleuth is the most accurate, flexible and trustworthy way to measure your team's Accelerate (DORA) performance

Understanding your teams change lead time allows you to spot bottlenecks. However, to really get to an understanding of what's going on you need to know where in your lead time time is spent.

You can now drill in to see a graph of your teams coding, review lag, review and deploy time. Just click the breakdown in your lead time graph and see which how your time is performing and which deploys have taken longest.

Spot your teams bottlenecks with Sleuth!

Show Previous EntriesShow Previous Entries