Announcing Team Sync for multiple GitHub accounts!

Sleuth's GitHub Team Sync feature now supports syncing teams across multiple GitHub organizations! 

Sleuth users can choose which GitHub organizations to include or exclude from Sleuth's automated Team Sync feature. Teams are automatically re-synced every 24 hours, and Sleuth users can also trigger a re-sync across all included GitHub organizations on demand.

Check out the Team Sync help doc article for more information.

Improved mono-repo support

Sleuth has supported mono-repo's for some time now by allowing you to specify a source path to include when configuring your code deployment.

However, customers work in highly varied ways and need complete flexibility to correctly capture how they're working. We've improved our mono-repo support by allowing for customers to specify multiple source paths to both include and exclude. Using a combination of these advanced fields teams can fully express how their mono-repos are deployed and capture accurate DORA metrics for each.

Start tracking DORA metrics for your mono-repo today!

Improved integrations experience, use your existing tools to track DORA metrics

Sleuth's integrations are how your Teams can start tracking DORA metrics in 5 minutes or less. Your team has already invested in the right tools, tools like GitHub, Jira, PagerDuty and more. Sleuth connects to the systems you've already invested in so you can get accurate and quality DORA metrics in minutes.

Our updated integrations experience now makes it easier to see what permissions you'll need when connecting a new integration, what still needs to be configured and what you've already enabled.

Setup Sleuth and discover your DORA metrics baseline today!

Auto-detect deploys and builds with Buildkite

We're excited to release our number one requested integration, a CI/CD integration with Buildkite! So many teams we speak to have gone all-in on Buildkite for their CI/CD needs.

With the Sleuth Buildkite integration you can now map Sleuth environments to Buildkite jobs for 100% accurate metrics without any modifications to your deployment process or scripts.

Once connected the integration also allows you to use any Buildkite jobs that run tests or static analysis as a build impact source to define your change failure.

Finally, you'll find that Sleuth will link deploy or test builds to your deploys, providing deep links and an integrated view in the deploy timeline.

Integrate your Buildkite CI/CD with Sleuth today!

Updated sidebar, quickly find your focus

We've updated our Sidebar navigation so your Sleuth experience is calmer and more focused. The slimmed down navigation allows you to quickly navigate to your top tasks; discovering your Organizations/Projects metrics and status.

Clicking through 'More' will still allow you to navigate to individual deployments and impacts. The navigation automatically expands and contracts to show your navigation context while you move through Sleuth and it remembers your last state, just in case you want to roll with the nav fully expanded.

Improved security and experience with our GitHub App

Sleuth now integrates with GitHub via a GitHub App. GitHub Apps allow organizations finer-grain control over the permissions and repositories that Sleuth has access to. The app has allowed us to remove some of the access scopes we'd required in the past, we now only require Read access for the repositories and Write access for Status and Actions. The app also allows for a higher API rate limit and allows you to connect as an Organization, not as a User.

Switching over to connecting to GitHub via the App is very simple and seamless. In Sleuth just navigate to your Integrations page, disconnect your existing GitHub integration, then reconnect. You'll be prompted to install and approve the GitHub app and away you go!

Note: Some organizations have setup GitHub to require internal approval to install an app. Check with your admins before disconnecting your existing integration.

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!

Show Previous EntriesShow Previous Entries