Metrics Dashboards: DORA Metrics

Updated 2 years ago by Betsy Rogers

All four of your DORA metrics are available for reporting in the DORA Metrics dashboard. To find this dashboard, go to the Metrics tab, and select "Dora Metrics" from the left menu of available dashboards.

Filtering your DORA Metrics report

Your DORA metrics dashboard can be filtered to display DORA metrics for specific date ranges, one or multiple teams, or specific repos. Use the filters at the top of your metrics report to select which team(s) or repos you'd like to investigate.

This main report will remember your team or repo selections between visits. You can make custom reports for any specific repo or set of teams you'd like to routinely report over. Creating custom reports allows you to add in additional metrics for further context, as well as customize the order and even colors displayed in these reports. You can learn more about making custom dashboards here: How Do I Build a Metrics Dashboard?

DORA Metrics

Cycle Time

The cycle-time metric in this dashboard will show the average cycle time for each day/week/month displayed, the top metric will be the average of all average cycle times displayed. Click into any data point to see the list of repos that specifically contributed to this cycle-time calculation.

For this graph, only completed branches will be summed and averaged. Branches that are in progress and do not have a complete cycle time calculation will not be included in this graph.

Deployment Frequency

LinearB calculates deployment frequency by counting the unique number of releases identified from your Git provider (via tags, merges, or API deployments based on your release detection settings) and dividing them by the number of days/weeks/months displayed in the graph.

MTTR

MTTR is a metric that represents the average time it takes to restore from a failure of the system or one of its components. LinearB calculates this metric based on the time between when a "production bug" is created in your project management tool, and the time this issue (ticket) is resolved.

This issue can be customized based on your by clicking the icon on this widget and updating LinearB to listen for your system-critical issues. You can read more about customizing your MTTR settings here: What is MTTR?

Haven't connected your PM tool yet? Lean how to here: Connect LinearB to your Project Management Platform

CFR

CFR is a metric that represents the percentage of deployments causing a failure in production. LinearB calculates this metric based on the number of "production incidents" defined in your project management tool divided by the number of deployments.

This issue can be customized based on your by clicking the icon on this widget and updating LinearB to listen for your production failure issues. You can read more about customizing your CFR settings here: What is CFR?