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.

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.

We're excited to announce the release of our most recent Incident integration, Atlassian Opsgenie!

With this integration you can now drive your change failure and MTTR via your Opsgenie incidents.

Just connect via your Opsgenie API key, configure in Sleuth and see your incidents reflected in your DORA metrics in moments!

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!

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 support@sleuth.io. 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.

Happy holidays from the Sleuth team! We've got a holiday treat for those of you who like to manage your configuration as code with Terraform.

With our new Sleuth Terraform provider you can now provision Sleuth Projects, Environments, Deployments and Impacts alongside any other critical infrastructure you team maintains.

Provision some Sleuth to bring in that holiday cheer today 🎁!

Are you using Jira Cloud, Jira Datacenter or Shortcut for incident management? If so, Sleuth can now automatically drive your change failure and MTTR via your existing incident workflow.

Just connect your issue tracker to Sleuth, provide a search query that captures your open incidents and let Sleuth do the rest! 

Are you using Statuspage to communicate with your customers when experiencing an incident? If so, you can now seamlessly drive your change failure and MTTR via your Statuspage incidents.

Just connect and configure in Sleuth and see your incidents reflected in your DORA metrics right away!

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.

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!