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!

"Accelerate" your team with Sleuth

Sleuth is now the most accurate, flexible and trustworthy way to measure your team's Accelerate (DORA) performance. With Sleuth’s new metrics experience engineering leaders have the insights they need to know how their team is performing, where they may be encountering bottlenecks and how to remove them. 

A new metrics dashboard, detailed breakdowns, industry standard rankings, actionable insights and the tools your developers need to improve means Sleuth will accelerate your team's development and deployments today!

Read more about it on our blog.

Rollbacks for a more powerful MTTR and change failure rate

As of today Sleuth knows when your team performs a code rollback! Just register a deploy with a revision that was previously deployed and Sleuth will jump into action!

When a code rollback is detected Sleuth creates a Rollback deploy that links to the deploys that were rolled back. Sleuth tags the rolled back deploys so you can easily search for them and changes their status to "Rolled back".

Sleuth is already the most accurate and flexible way to track your team's Accelerate metrics. With the addition of rollbacks your MTTR and change failure calculations have become even more powerful. Rollbacks count toward your teams MTTR and change failure rate.

Start tracking your teams rollbacks today!

Use Sleuth with any public or private Git repository

Sleuth can now track deployments and metrics for any git repository, including those behind a firewall. Instead of connecting to your GitHub or Bitbucket repositories and retrieving information, there is now a "Custom Git" repository type option that lets you use a CLI tool, sleuth-client, to push commit information into Sleuth, giving you full control over what source code information Sleuth sees.

To use it, select the option into the drop down:

After the code deployment source is created, use the  sleuth-client to register deploys:

For more information, see the documentation

Show Previous EntriesShow Previous Entries