The Sleuth Slack integration just leveled up! We're excited to introduce the Sleuth Slack slash command.

Have you ever been in your standup and wondered if your PR has shipped? Just ask Sleuth from the comfort of your Slack client and never wonder again.

By default /sleuth MY SEARCH TEXT will search your projects for matching deploys. You can also use the /sleuth create My manual change #with_tags command to create manual changes.

Just update to the latest version of our Slack app and connect your Sleuth account to your Slack to start using the Sleuth slash command today!

We've upgraded our Sentry integration to ensure that every release is paired with error tracking and release health is surfaced to the developer. You can now drill down through a release in Sentry to understand the cause of errors and understand in nuanced detail the health metrics of your releases over time. And with our recent updates, you can now publish releases directly to Sentry from Sleuth. Check out the video below to learn more! 

Sleuth now uses role-based access controls (RBAC) to restrict access to the Sleuth application. Depending on the given role (Owner, Administrator, Developer, or Observer), members within the organization can handle billing, add new members and assign roles, adjust settings for integrations and deployments, or can simply be read-only viewers of the Dashboard. 

For more information, read more about Access Control in our documentation.

With the new Automatic Tags feature, Sleuth can surface deployments that matter most to you and your team—automatically. Learn more about how Automatic Tags work and how you can create your own by reading this blog post and watching the video with Sleuth CTO Don Brown. 

If you have been representing environments with multiple projects in Sleuth, fret no more: Sleuth now offers first-class environment support, and we couldn't be more excited! Be sure to watch CTO Don Brown's awesome video and read his blog post on Sleuth's new first-class Environment support!

 

Sleuth's environment support allows you to track changes across environments within a project to understand what state each environment is in, and also to know when and what changes are shipping to production. Switching between environments is as easy as switching between projects, using the selector shown above. 

Existing users don't need to do anything. After logging in, you will see both a Production and Staging environment in your Sleuth projects, with the Production environment set as the default. You can change this and other settings (for example, a master branch mapped to Production, a different branch mapped to Staging, etc.) to accommodate your development workflow.

Read more about Sleuth Environment Support and how to configure Environments in your Project Settings. 

Happy deploying!

Our FREE and STANDARD plans both provide up to 50 deploys per month, with 25 additional deploys at only US$25. We can also tailor a CUSTOM plan for you if those don’t work for you. 

For more information, visit our updated Pricing page. You’re sure to find a plan that works for you and your team. 

Impact tracking in Sleuth uses your key SLIs to let you know if your deploys are getting the job done or causing new problems in real-time.

Impact tracking just got more powerful with the addition of our Datadog and SignalFx integrations.

Connecting the Datadog and SignalFx integrations, like other Sleuth integrations, couldn’t be simpler. Read our Datadog and SignalFx help pages for information on the integration and how to set it up.  

You can then head to the Dashboard to see your Datadog and SignalFx metrics and the impact of your deploys in action, in real-time.

Learn more about how Sleuth tracks impact and keeps your team informed by reading our CEO Dylan Etkin’s blog post: Real-time Impact Tracking and Notifications.

Sleuth’s new personal Slack notifications means that you'll be notified instantly when your code or changes that you were involved in ship.

No more long-polling your build system to see if that code finally made it out to production. Or checking your Jira instance to see if the issues has been moved to done (who remembers to update their Jira issues, right?).

If you've configured Impact for your deploys and Sleuth detects that your change was unhealthy, you'll know moments after deploy. Finally, developers can see the impact of their changes in real-time! Without having to leave the comfort of their Slack client 😀.