Sleuth is your single pane of glass for deploys. CI/CD builds are your DevOps workhorse, used for testing and deploying your changes, and are now automatically visible for every deploy. We've added integrations for our most requested providers in Jenkins, Github Actions, CircleCi and Bitbucket pipelines. More CI/CD integrations are on the way, just reach out if you don't see your provider on our list.

The integration also allows Sleuth to trigger your existing builds via our Sleuth Actions. Use Sleuth to setup your perfect deployment workflow. Your team can use Sleuth's deployment verification to trigger promotion between environments or auto-trigger rollbacks. With build triggers you can setup Slack based approvals to drive your change failure rate to zero.

Link your CI/CD builds today!

Hot on the heals of Sleuth search we had added many quick and contextual ways to find the exact deploy you are looking for from the Sleuth UI. Click and drag on any Sleuth trend graphs to see the deploys behind the trend.

We've also linked many of the elements you see in the Sleuth UI such as; deploy tags, authors and size such that they will take you to the Sleuth search with pre-filled filters for the attribute you clicked and its associated context.

Insights and trends are now just a click away!

Sleuth connects to your error trackers and cloud-based metrics trackers to auto-verify the health of your deploys so your team can drive MTTD (mean time to detection) to zero!

Today, with the grounds up rewrite of our anomaly detection algorithm, our Impact tracking is now 200% more accurate. 

Our new Impact graphs allow you to quickly see how deploys affect your metrics and see how Sleuth has determined their health.

We've also added the ability to manually specify your healthy threshold for those teams with amazing house-keeping, where your impact measures never really reach anomalous levels . So if you want to measure your database CPU, but really only care if it goes over 50%, you can tell Sleuth and we'll only alert you once it's breached that threshold.

These changes, coupled with our recent support for AWS CloudWatch,  NewRelic and Custom impact sources, means there's nothing stoping your team from driving your MTTD to zero with Sleuth today!

One of the most popular topic's to come from the Accelerate DevOps book is the “four measures of software delivery performance”, sometimes called “Accelerate metrics” or the DORA metrics.

The metrics; deployment frequency, change lead time, change failure rate and mean time to recovery (MTTR) are indicators of a DevOps teams health and its ability to quickly and safely deploy changes.

But how can your team track these metics? Your Sleuth project dashboard does all the heavy lifting for you. 

Because Sleuth knows when you deploy and verifies your deploy health we can automatically generate a high-fidelity view into your Accelerate metrics. Once you know your baseline let Sleuth provide the tools you need to improve!

Sleuth now provides individuals a daily, weekly, bi-weekly or monthly summary of what was deployed, delivered right to you via Slack! 

This is an especially powerful feature for engineering managers, product manager, support member or anyone trying to keep track, at a high level, of what's deploying. Sleuth allows you to request a report at the project or deployment level so you can get only the information that matters to you.

This adds to Sleuth's Slack mission control which allows you to control your deploys right from the comfort of Slack.

Impact tracking in Sleuth uses your key SLIs to verify your deploys are getting the job done!

Impact tracking just got more powerful with the addition of our New Relic and Custom, user provided impact, integrations.

Connecting the NewRelic integration, like other Sleuth integrations, couldn’t be simpler. Read our New Relic and Custom Impact help pages for information on the integrations and how to set them up.

Once configured Sleuth automatically verifies the health of your deploys. Via our health indicators you can see 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.

Our redesign started with our updated project Command Center and was quickly followed with our updated deployment dashboard. Today we've rolled out the last phase of our updates with a redesigned deploy details view.

The deploy details view allows developers to instantly troubleshoot bad deploys with:

• Who made the change and the authors involved
• What changed and how it came to be with links to the code diff and related issues
• When the change was deployed and when it was superseded 
• A clear view into the health and impact of the deploy

Following on the heels of our project Command Center update today we’re excited to be rolling out a completely redesigned deployment dashboard. We've brought all the improvements from our project command center and more to your deployment view.

The deployment dashboard provides developers:

• A preview of what you're about to deploy
• Help keeping your environments in sync
• A powerful search to quickly find previous deploys

Head on over and check out your new deployment dashboard!

Today we’re excited to be rolling out a completely redesigned Sleuth experience. Our updated Command Center provides one place to visit so developers can quickly and safely deploy new changes.

Command Center has been designed for developers so that at a glance you can:

• Deploy new changes quickly and safely
• Preview what you're about to deploy
• Easily keep your environments in sync

If you haven't recently visited your dashboard, it's time to take another look!

It's clear you all love Slack notifications for your deploys. However, we knew we could do better at making it immediately obvious what changed, when it happened and who was responsible.

Every notification now starts with a quickly identifiable emoji so you can understand what kind of event occurred and a deep link to Sleuth to find out more. Next we put the "what" of the change front and center. Finally, messages call out the author and any important attributes of the notification.