Deploy frequency

Search…
Deploy frequency
Sleuth shows you the deploy frequency for all code deployments and feature flags you've setup within a project and environment. Sleuth allows you to see your deploy frequency for each environment you maintain.‌
Batch size breakdowns
The Sleuth project metrics dashboard shows the total number of deploys and the frequency, deploys per day, in the period. We provide a detailed breakdown of the batch size of each deploy as a percentage of the total and broken down per day. Batch size is defined as a blend of the number of pull requests, the number of commits and the amount of code changed, weighted in that order. Batch sizes are defined as: 
Small - usually 1 pull request, 1 - 10 commits and a few hundred lines of code changed 
Medium - usually 1 - 2 pull requests, 10 - 30 commits and many hundreds of lines of code changed
Large - usually 2 - 4 pull requests, 20 - 40 commits and many hundreds of lines of code changed
Gigantic - usually 4 or more pull requests or 30 or more commits or many thousands of lines of code changed
Because batch size is a weighted blend of pull requests, commits and code changes you can find that an especially large amount of change in any of those elements can cause a deploy to be classified as Large or Gigantic.
Feature flags and frequency
Sleuth supports feature flags as a first class form of change. That said, we find that teams want to understand the distinction between their code deploy frequency and their flag change frequency. The Sleuth metrics dashboard shows the two frequencies as separate graph lines and allows you to toggle on or the other on and off. To see totals for flag frequency you can hover over a data point. 
Setting up deploy frequency
Sleuth uses our code integrations (Github, Bitbucket, Gitlab, etc) coupled with our deployment tracking to understand when you've deployed. Once you've connected your code to Sleuth, setup your first Code Deployment and started registering deploys Sleuth will automatically track your deploy frequency and batch size breakdown for each deploy to each of your defined Environments.
Sleuth uses our LaunchDarkly integration to track feature flag changes. Once setup, we'll automatically start tracking your flag frequency across each of your defined Environments. 
For the most accurate metrics we recommend using a webhook to register your deploys. Initially Sleuth is configured to count a pull request merge as a deploy until we've received your first webhook.
Change lead time
Change failure rate
Last modified 2mo ago
Copy link
Contents
Batch size breakdowns
Feature flags and frequency
Setting up deploy frequency