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!

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 😀.