Use Sleuth with any public or private Git repository

Sleuth can now track deployments and metrics for any git repository, including those behind a firewall. Instead of connecting to your GitHub or Bitbucket repositories and retrieving information, there is now a "Custom Git" repository type option that lets you use a CLI tool, sleuth-client, to push commit information into Sleuth, giving you full control over what source code information Sleuth sees.

To use it, select the option into the drop down:

After the code deployment source is created, use the  sleuth-client to register deploys:

For more information, see the documentation

Keep your change failure rate low with Slack based approvals

For teams with pre-production environments a great way to keep your change failure rate low is to pause and require developer approval before promoting changes to production. Sleuth has your team covered with the introduction of Slack based deployment approvals.

Sleuth approvals live where your teams work, in Slack. Authors of change are mentioned and votes are updated in the Slack message and within Sleuth. Approvals link to our powerful Slack team deploy notifications so you have all the context you need, right in Slack.

Approvals are super flexible and can be adjusted to meet your team's needs. Specify a soak time and we'll only prompt for an approval once met. Have Sleuth enforce a minimum number of approvers and whether those need to be the authors involved in the change or just anyone on your team. 

The actions Sleuth takes on a successful approval are flexible as well. We have built in actions for triggering builds with Github Actions, Bitbucket pipelines and CircleCI. However, it doesn't stop there, you can trigger any supported actions after approval.

Drive your change failure rate to zero with Slack based approvals today!

Get a 50-Foot view with your Organization dashboard

Sleuth's project dashboard is where you go to quickly and safely deploy new changes. However, sometimes you want a higher-level view across all your Organization's projects. Sleuth's new organization dashboard is here to help!  

Your organization dashboard gives you a quick overview of the default environment for each of your projects so you can:

  • Compare and contrast your project's Accelerate metrics
  • See the overall health of your organization's deploys 
  • Get a snapshot view into exactly what's been changing across your projects

Your organization dashboard can be accessed via the options in the top right Organization switcher by choosing the "Organization dashboard" link from the menu.

Drill in to discover the why behind your trends

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 search makes you a super sleuth!

No good sleuth should be without an amazing magnifying glass. Sleuth's new search is now the most powerful tool in your kit, allowing you to instantly find the cause of any bad deploys.

Search allows you to quickly drop in a commit hash, issue key, tag and much more to find when a deploy rolled out to all your environments. Combine filters to slice and dice your way to the answer you're looking for.

We've included a new list view of your deploys so you can dig into your changes, hunting for that elusive root cause, without distraction.

See what you can discover with search today!

New Relic and custom Impact tracking

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.

What did I do yesterday? Try Sleuth Standup

Tired of trying to remember what you did yesterday? Me too. With some 20% time, I added a simple Sleuth Slack command that help you build your standup report, prepopulating it with your deployments and other development activity. Run this in any Slack channel:

/sleuth standup

And you'll see a dialog that when submitted, reports your standup to the channel:

To see more than the last 24 hours, try appending a time period after the command, for example, this command will return the last 3 days:

/sleuth standup 3d

To see it in action, check out this "commercial": 

Model impact release with Sentry

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! 

Role-Based Access Control (RBAC) Support

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.


Show Previous EntriesShow Previous Entries