localurl:/docs/dashboards/dora-metrics/

-title:Dashboards & insights

icon:images/home-icons/guides.png

url:''

links:

-title:Home dashboard

localurl:/docs/dashboards/home-dashboard/

-title:DORA metrics

localurl:/docs/dashboards/dora-metrics/

-title:CI/CD guides

icon:images/home-icons/guides.png

-title:Dashboards & Insights

url:"/dashboards"

pages:

-title:Home dashboard

url:"/home-dashboard"

-title:DORA metrics

url:"/dora-metrics"

-title:Dashboards & Insights

url:"/dashboards"

pages:

title:"DORA metrics"

description:"Get insights into your deployments"

group:dashboards

toc:true

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](https://www.devops-research.com/research.html#capabilities){:target="\_blank"} (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

[Read more on DORA](https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance){:target="\_blank"}.

Monitoring DORA metrics can help identify delivery issues in your organization by detecting bottlenecks among teams and 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](https://g.codefresh.io/2.0/dora-dashboard/dora){:target="\_blank"}.

{% include

image.html

lightbox="true"

file="/images/reporting/dora-metrics.png"

url="/images/reporting/dora-metrics.png"

alt="DORA metrics report"

caption="DORA metrics report"

max-width="100%"

%}

Use filters to define the exact subset of applications you are interested in. All filters support auto-complete and multiselect.

More than one option within the same filter type has an OR relationship. Multiple filter types 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

If you have[starred applications as favorites]({{site.baseurl}}/docs/deployment/applications-dashboard/#applications-dashboard-information) in the Applications dashboard, clicking {::nomarkdown}<imgsrc="../../../images/icons/icon-mark-favorite.png?display=inline-block">{:/} in DORA metrics, displays DORA 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:

* Deployments

* Rollbacks

* Commits/Pull Requests

* Failure Rate: The number of failed deployments divided by the total number of deployments

The metric graphs are key to performance insights with DORA metrics. The metrics are 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:

* Daily

* Weekly

* Monthly

Remember that the graphs for the DORA metrics reflect metrics of application deployments, not workflows.

**Deployment Frequency**

The frequency at which applications are deployed to production, including both successful (Healthy) and failed (Degraded), deployments. A deployment is considered an Argo CD sync where there was a change in the application source code that resulted in a new deployment of the application to production.

The X-axis charts the time based on the granularity selected, and the Y-axis charts the number of deployments. The number shown on the top right is the average deployment frequency based on granularity.

**Lead Time for Changes**

The average number of days from the first commit for a PR (pull request) until the deployment date for the same PR. The key term here is_deployment_. Lead Time for Changes considers only those changes to workflows that result in a deployment. Making a change to a repo that does not result in a deployment is not included when calculating Lead Time for Changes.

The X-axis charts the time based on the granularity selected, 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.

**Change Failure Rate**

The failure or rollback rate in percentage for applications whose health status changed to Degraded on deployment. The key term here is_on deployment_. For example, bumping an image tag with one that does not exist, results in the application being Degraded on deployment, and designated as failed.

The Change Failure Rate is derived by dividing the number of Degraded (failed/rollback) deployments with the total number of deployments.

The X-axis charts the time based on the granularity selected, and the Y-axis charts the failure rate. The number shown on the top right is the average failure rate based on granularity, and therefore may not be equal to the Total Failure Rate.

**Time to Restore Service**

The average number of hours taken for the status of Degraded deployments to return to Healthy. Again, similar to the Change Failure Rate, Time to Restore Service includes only deployments that became Degraded. It is derived by dividing the total number of hours for all Degraded deployments to return to Healthy by the total number of Degraded deployments.

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.

[Global analytics dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard)

[Monitoring applications]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/)

title:"Global analytics dashboard"

description:""

group:dashboards

toc:true

Get a global picture of runtimes, managed clusters, deployments, and pipelines in the Home dashboard. The Home dashboard is displayed when you log in to Codefresh, providing system-wide visualization in real-time.

Global filters allow you to narrow the scope of the data, and drill down into specific entities for more details.

{% include

image.html

lightbox="true"

file="/images/reporting/home-dashboard.png"

url="/images/reporting/home-dashboard.png"

alt="Home dashboard: Global enterprise analytics"

caption="Home dashboard: Global enterprise analytics"

max-width="70%"

%}

Filter the view in the Home dashboard by runtimes and date range.

{% include

image.html

lightbox="true"

file="/images/reporting/global-filters.png"

url="/images/reporting/global-filters.png"

alt="Home dashboard: Global filters"

caption="Home dashboard: Global filters"

max-width="60%"

%}

Identify the health of the runtimes and managed clusters in your enterprise.

Health status is displayed for both hosted (if you have Hosted GitOps), and hybrid runtimes.

Managed clusters are external clusters registered to runtimes to which you deploy applications and GitOps-managed resources.

{% include

image.html

lightbox="true"

file="/images/reporting/runtimes-clusters-widgets.png"

url="/images/reporting/runtimes-clusters-widgets.png"

alt="Runtimes and Managed Clusters in the Home dashboard"

caption="Runtimes and Managed Clusters in the Home dashboard"

max-width="80%"

%}

{: .table .table-bordered .table-hover}

| Item| Description|

| ------------------------| ----------------|

|**Runtimes**| Identify failed runtimes.|

|**Managed Clusters**|{::nomarkdown} <ul><li><b>Status</b>: One of the following: <ul><li><b>Connected</b>: Argo CD is able to connect and successfully deploy resources to the cluster.</li><li><b>Failed</b>: Argo CD is unable to connect to the cluster because of authentication, networking, or other issues. </li> <li> <b>Unknown</b>: Argo CD has no information on the cluster as there are no resources deployed to the managed cluster.</li></ul><li><b>View</b>: Click to go to the Runtimes page. <br>To see the runtime's managed clusters, select the runtime.</li> </ul> {:/}|

Identify trends for deployments.

{% include

image.html

lightbox="true"

file="/images/reporting/deployments-widget.png"

url="/images/reporting/deployments-widget.png"

alt="Deployments in the Home dashboard"

caption="Deployments in the Home dashboard"

max-width="70%"

%}

{: .table .table-bordered .table-hover}

| Item| Description|

| ------------------------| ----------------|

|**Daily/Weekly/Monthly**| Granularity for deployment views that affects the average number of deployments and the comparison to the reference period.|

|**Number and Comparison Average**| The number on the top right is the number of successful/failed/rollback deployments for the selected granularity. The percentage is the comparison to the reference period, also for the selected granularity.|

|**Successful**| The number of successful deployments per day, week, or month according to the selected granularity.|

|**Failed Deployments**| The number of successful deployments per day, week, or month according to the selected granularity.|

|**Rollbacks**| The number of successful deployments per day, week, or month according to the selected granularity.|

Displays up to five of the most active applications and their current deployment status.

{% include

image.html

lightbox="true"

file="/images/reporting/applications-widget.png"

url="/images/reporting/applications-widget.png"

alt="Applications in the Home dashboard"

caption="Applications in the Home dashboard"

max-width="70%"

%}

{: .table .table-bordered .table-hover}

| Item| Description|

| ------------------------| ----------------|

|**Filter**| Filter applications by the cluster on which they are deployed.|

|**View**| Click to go to the Applications dashboard. See|

|**Application Name**| The name of the application, and the names of the runtime and cluster on which it is deployed. Click the name to drill down into the application in the Applications dashboard.|

|**Health status**| The health status of the application, and can be either:{::nomarkdown}<ul><li>Healthy (green): The application is running on the cluster.</li><li>Degraded (red): The application failed to run.</li> <li>Rollback (yellow): There was a rollback to the previously deployed version.</li></ul> To see the breakdown by health status, mouse over the chart. <br> The number at the end of the bar is the total number of deployments for the application, with the overall decrease or increase compared to the reference period. {:/}|

Displays all active pipelines for the selected date range, providing insights into trends for pipelines. Active pipelines are those with at least one active or completed workflow.

Analytics are derived by comparing the selected date range to the corresponding reference period. If your date range is the last seven days, the reference period is the seven days that precede the date range.

{% include

image.html

lightbox="true"

file="/images/reporting/delivery-pipeline-widget.png"

url="/images/reporting/delivery-pipeline-widget.png"

alt="Delivery Pipelines in the Home dashboard"

caption="Delivery Pipelines in the Home dashboard"

max-width="80%"

%}

{: .table .table-bordered .table-hover}

| Item| Description|

| ------------------------| ----------------|

|**Pipelines**| The number prefixed to the pipeline name indicates the change in position of the pipeline compared to the reference period. To drill down into a specific pipeline, click the pipeline.|

|**Filter**| The filters available to focus on the pipelines of interest:{::nomarkdown}<ul><li><b>Status</b>:<ul><li>Succeeded: Pipelines with workflows completed successfully.</li><li>Failed: Pipelines with workflows that failed.</li><li>Error: Pipelines with workflows that resulted in errors.</li></ul><li><b>Repository</b>: The Git repository or repositories tracked, with the events that triggered or ran the pipelines.</li><li><b>Event Type</b>: The Git or Calendar event or events by which to view pipelines. If you select Git push, only those pipelines configured to be run on Git push are displayed.</li> <li><b>Initiator</b>: The user who made the commit that triggered the event and caused the pipeline to run.</li></ul>{:/}|

|**View**| Click to go to the Delivery Pipelines dashboard.|

|**KPI Averages**| KPI averages for: {::nomarkdown}<ul><li>Success Rate: The average number of successful executions, in percentage.</li><li>Average Duration: The average length of time to complete execution, in mm:ss.</li> <li>Executions: The average number of times the pipeline was triggered, in percentage.</li><li>Committers: The number of users whose commits on the repository or repositories triggered the pipelines. User count is aggregated per user, so multiple commits from the same user are counted as a single commit.</li></ul> To see detailed day-to-day values, select a line chart.{:/}|

|**Most Active Delivery Pipelines**| Up to ten pipelines with the highest number of executions. The same KPIs are displayed, and compared to those in the reference period.|

|**Longest Delivery Pipelines**| Up to ten pipelines with the longest duration. The same KPIs are displayed, and compared to those in the reference period.|

[DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/)

[Monitoring applications]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/)

[Images in Codefresh]({{site.baseurl}}/docs/deployments/gitops/images/)