For a lot of us, Slack is now where work gets done. We use Slack to pull together the notifications and discussions teams need to keep projects moving forward. Remote DevOps teams remain connected and engaged and can move quickly, like a good agile team should, to address deployment issues as they arise.
Slack notifications can rise above the noise generated by the usual low-fi channels (i.e., e-mail, SMS, etc), keeping you and your teams laser-focused on delivering high-quality applications to your users. Sleuth offers a robust Slack integration that keeps your teams informed about how your deploys are impacting your code over time. Know right away if there are any issues—teams are instantly notified via Slack if there’s a problem with your deployment. And it’s not just a simple, cryptic e-mail with “Something’s wrong!” in the subject line.
The Slack notification Sleuth delivers gives everyone the information they need to address the issue.
Find out instantly what code deployed, and when; the size of the deploy; who deployed the code (and who might be able to fix it if there’s an issue); and a link to the GitHub or Bitbucket hash. Or, go straight to the Sleuth Dashboard to get a more detailed look at what happened and where you need to go to fix it.
With the current office communications model, developers can be inundated with a barrage of emails and messages from various DevOps tools when something goes wrong. No more clicking through multiple browser tabs opened to your CI/CD SaaS tool instances to find out which one caused the unhealthy deploy. With the Slack integration in Sleuth, you (and/or your team) receive focused messages, cutting down on wasted time trying to figure out which alarms are sounding.
After creating your channels in Slack, you setup channel-based notifications for your teams and individual notifications for when something occurs that affects you or another team member specifically. You can configure messages to reach your entire DevOps team or only those involved in authoring and/or committing the code that just deployed. Some channels might target your developers, who might want to receive all notifications on the progress of their deploys; product managers might only be concerned with large deploys that might signal an upcoming update; maybe your CTO only wants to know when the server is about to blow up due to a slew of ailing deploys. Instead of a river of equally-weighted emails all telling you the same thing, Sleuth's Slack notifications target a specific audience and provide them with all the information they need (or don’t need) to know.
Head over to Sleuth Documentation to find out how to set up the Slack integration. Happy deploying!