In our ongoing effort to maintain alignment with the State of DevOps report, we've removed the "Elite" category from Sleuth's performance cards, digest emails, and all other places where it previously appeared.
Check out the 2022 State of DevOps Report for more on this and other findings!
You can now start your CLT clock based on state changes in your issue tracker!
By expanding your CLT lens to include your issue tracking workflow, issue-initiated CLT helps you identify and remediate pre-commit bottlenecks and their impacts to your overall coding time.
Check out this blog post for an in-depth discussion on why you might want to enable this new option, and if you decide it might be the right choice for your team, check out this help doc for instructions on how to enable and configure it for one or more of your Sleuth projects!
Sleuth's GitHub Team Sync feature now supports syncing teams across multiple GitHub organizations!
Check out the Team Sync help doc article for more information.
For more on how to set up and use the integration, refer to our ServiceNow integration help doc!
While Sleuth has always provided powerful cross-org and project-level efficiency analytics, we're pleased to announce an exciting new set of features that focus on enabling our customers to measure, compare, and drive efficiency improvements through a team-centric lens 🔎
With this release, Sleuth users can now:
For more on how you best leverage these features to rally your teams around team-centric metrics, check out our latest blog post, Announcing DORA Metrics for Teams!
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!
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!
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!
Are you using Datadog monitors for alerting? If so, Sleuth can now automatically drive your change failure and MTTR via your existing alerts.
Just connect your Datadog instance to Sleuth, provide a monitor query that captures the alerts that matter to you and let Sleuth do the rest!
We've expanded our Incident integration's once again with our new Blameless integration!
With this integration you can now drive your change failure and MTTR via your Blameless incidents.
