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.

Organizations use DORA metrics to have a set of hard numbers that illuminate the performance of their engineering efficiency. 

With Sleuth's new Trends and Compare dashboards you now have the power to answer engineering efficiency questions across your entire Organization.

Trends

Compare

Our new Project labels allow you to create flexible taxonomies to slice and dice your DORA metrics across your Organization. Group your projects by coding language, sprint time or whatever dimension you need insights on.

The Trends dashboard allows you spot how your initiatives are trending over time.

With the Compare dashboard you can determine the relative impact of your Engineering initiatives and processes. Do you want to see how your Java-based projects compare to your Python-based projects? Perhaps you’d like to know how your TDD teams stack up against non-TDD teams. Are one week or two week sprints more efficient? 

Let Sleuth provide the real-world answers to your Engineering-wide questions!

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!

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 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!

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!

We're excited to announce the release of our most requested integration, PagerDuty!

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

Just connect via OAuth, configure in Sleuth and see your incidents reflected in your DORA metrics in minutes!