Get insights into your deployments
DevOps is a collaboration paradigm that is sometimes mistaken for being too abstract or too generic. In an effort to quantify the benefits of adopting DevOps, Dora Research (acquired by Google in 2018), has introduced four key metrics that define specific goals for improving the software lifecycle in companies interested in adopting DevOps.
DORA measures these metrics:
- Deployment Frequency: How often an organization successfully releases to production
- Lead Time for Changes: The length of time for a commit to be deployed into production
- Change Failure Rate: The percentage of deployments causing a failure in production
- Time to Restore Service: The length of time for an organization to recover from a failure in production
DORA metrics in Codefreh
Monitoring DORA metrics can help identify delivery issues in your organization by detecting bottlenecks among teams, and help to optimize your workflows, at technical or organizational levels.
Codefresh offers support for DORA metrics out of the box.
- In the Codefresh UI, go to DORA metrics.
Use filters to define the exact subset of applications you are interested in. All filters support auto-complete and multi-select. More than one option within the same filter type has an OR relationship. More than one filter type when defined share an AND relationship.
- Runtimes: Show metrics for applications from selected runtimes
- Clusters: Show metrics for applications deployed to selected clusters
- Applications: Show metrics for selected applications.
- Time: Show metrics from application for a specific time period
When no filters are defined, all metrics are shown for the last 90 days.
Metrics for favorite applications
If you have starred applications as favorites in the Applications dashboard, clicking in DORA metrics, displays metrics only for those applications.
As the title indicates, the Totals bar shows the total numbers, based on the filters defined, or for the last 90 days, if there are no filters:
- Commits/Pull Requests
- Failure Rate: The number of failed deployments divided by the total number of deployments
The metric graphs show performance for the DORA metrics, again based on the filters defined, or for the last 90 days, if there are no filters.
In addition, you can select the granularity for each graph:
The frequency of deployments of any kind, successful or failed. Deployment is considered an Argo CD sync where there was a change. The X-axis charts the time based on the granularity, and the Y-axis charts the number of deployments. The number shown on the top right is the average deployment frequency based on granularity.
Change failure rate
The failure or rollback rate in percentage for deployments. Derived by dividing the failed/rollback deployments by the total number of deployments. Failed deployments are those Argo CD deployments that lead to a sync state of Degraded. The X-axis charts the time based on the granularity, and the Y-axis charts the failure rate. The number shown on the top right is the average failure rate based on granularity.
Lead Time for Changes
The average number of days from the first commit for a pull request until the deployment date for the same pull request. The X-axis charts the time based on the granularity, and the Y-axis charts the time in minutes until the deployment. The number shown on the top right is the average number of days for a commit to reach production.
Time to Restore Service
The average number of hours between the change in status to Degraded or Unhealthy after deployment, and back to Healthy. The X-axis charts the time based on the granularity, and the Y-axis charts the time in hours. The number shown on the top right is the average number of hours between the previous deployment and rollback for the same application.