You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/dashboards/dora-metrics.md
+13-8Lines changed: 13 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ DORA measures these metrics:
21
21
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.
22
22
Codefresh offers support for DORA metrics out of the box.
23
23
24
-
* In the Codefresh UI,go to[DORA metrics](https://g.codefresh.io/2.0/dora-dashboard/dora){:target="\_blank"}.
24
+
* In the Codefresh UI,from Artifacts & Insights in the sidebar, select[DORA metrics](https://g.codefresh.io/2.0/dora-dashboard/dora){:target="\_blank"}.
25
25
26
26
{% include
27
27
image.html
@@ -69,24 +69,29 @@ In addition, you can select the granularity for each graph:
69
69
>Tip:
70
70
Remember that the graphs for the DORA metrics reflect metrics of application deployments, not workflows.
71
71
72
-
**Deployment Frequency**
72
+
###Deployment Frequency
73
73
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.
74
+
74
75
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.
75
76
76
-
**Lead Time for Changes**
77
-
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.
78
-
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.
77
+
###Lead Time for Changes
78
+
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.
79
+
80
+
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.
79
81
80
-
**Change Failure Rate**
82
+
###Change Failure Rate
81
83
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.
84
+
85
+
82
86
The Change Failure Rate is derived by dividing the number of Degraded (failed/rollback) deployments with the total number of deployments.
83
87
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.
84
88
85
-
**Time to Restore Service**
89
+
###Time to Restore Service
86
90
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.
91
+
87
92
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.
Copy file name to clipboardExpand all lines: _docs/dashboards/home-dashboard.md
+19-43Lines changed: 19 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,41 +1,41 @@
1
1
---
2
-
title:"Global analytics dashboard"
2
+
title:"GitOps Overview dashboard"
3
3
description:""
4
4
group:dashboards
5
5
toc:true
6
6
---
7
7
8
-
Get a global picture of runtimes, managed clusters, deployments, andpipelines in theHomedashboard.The Home dashboard is displayed when you log in to Codefresh, providingsystem-wide visualization in real-time.
8
+
Get a global picture of runtimes, managed clusters, deployments, andapplications in theGitOps Overviewdashboard.Getsystem-wide visualization in real-time for GitOps.
9
9
10
-
Global filters allow you to narrow the scope of the data, anddrill down into specific entities for more details.
10
+
Global filters allow you to narrow the scope of the data, and drill down into specific entities for more details.
11
11
12
12
{% include
13
13
image.html
14
14
lightbox="true"
15
-
file="/images/reporting/home-dashboard.png"
16
-
url="/images/reporting/home-dashboard.png"
17
-
alt="Homedashboard: Global enterprise analytics"
18
-
caption="Homedashboard: Global enterprise analytics"
alt="Runtimes and Managed Clusters in theHome dashboard"
48
-
caption="Runtimes and Managed Clusters in theHome dashboard"
47
+
alt="Runtimes and Managed Clusters in theGitOps Overview dashboard"
48
+
caption="Runtimes and Managed Clusters in theGitOps Overview dashboard"
49
49
max-width="80%"
50
50
%}
51
51
@@ -60,13 +60,15 @@ Managed clusters are external clusters registered to runtimes to which you deplo
60
60
61
61
Identify trends for deployments.
62
62
63
+
<!--- ask if to add here that only those changes that resulted in deployments are shown-->
64
+
63
65
{% include
64
66
image.html
65
67
lightbox="true"
66
68
file="/images/reporting/deployments-widget.png"
67
69
url="/images/reporting/deployments-widget.png"
68
-
alt="Deployments in theHome dashboard"
69
-
caption="Deployments in theHome dashboard"
70
+
alt="Deployments in theGitOps Overview dashboard"
71
+
caption="Deployments in theGitOps Overview dashboard"
70
72
max-width="70%"
71
73
%}
72
74
@@ -90,8 +92,8 @@ Displays up to five of the most active applications and their current deployment
90
92
lightbox="true"
91
93
file="/images/reporting/applications-widget.png"
92
94
url="/images/reporting/applications-widget.png"
93
-
alt="Applications in theHome dashboard"
94
-
caption="Applications in theHome dashboard"
95
+
alt="Applications in theGitOps Overview dashboard"
96
+
caption="Applications in theGitOps Overview dashboard"
95
97
max-width="70%"
96
98
%}
97
99
@@ -106,33 +108,7 @@ Displays up to five of the most active applications and their current deployment
106
108
107
109
108
110
109
-
###Delivery Pipelines
110
-
111
-
>Delivery Pipline data is shown for hybrid enviroments.
112
111
113
-
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.
114
-
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.
caption="Delivery Pipelines in the Home dashboard"
123
-
max-width="80%"
124
-
%}
125
-
126
-
{: .table .table-bordered .table-hover}
127
-
128
-
| Item| Description|
129
-
| ------------------------| ----------------|
130
-
|**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.|
131
-
|**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>{:/}|
132
-
|**View**| Click to go to the Delivery Pipelines dashboard.|
133
-
|**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.{:/}|
134
-
|**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.|
135
-
|**Longest Delivery Pipelines**| Up to ten pipelines with the longest duration. The same KPIs are displayed, and compared to those in the reference period.|
Copy file name to clipboardExpand all lines: _docs/getting-started/gitops-codefresh.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ See [Creating]({{site.baseurl}}/docs/deployments/gitops/create-application/) and
69
69
70
70
71
71
Once deployed, our dashboards give you enterprise-wide visibility into deployments, and key metrics.
72
-
From global analytics on applications and deployments (Home dashboard), to failure rate and lead time for changes (DORA dashboard), to application configuration, resource, and rollout management (Applications dashboard).
72
+
From global analytics on applications and deployments (), to failure rate and lead time for changes (DORA dashboard), to application configuration, resource, and rollout management (Applications dashboard).
Copy file name to clipboardExpand all lines: _docs/integrations/codefresh-hosted-gitops.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ redirect_from:
7
7
toc:true
8
8
---
9
9
10
-
Integrate CodefreshCI pipelines with Hosted GitOps for deployments powered by managed Argo CD.
10
+
Integrate Codefresh pipelines with Hosted GitOps for deployments powered by managed Argo CD.
11
11
12
12
13
13
Codefresh Hosted GitOps includes a dedicated report image step that both reports and enriches deployed images. Add the report image step in your Codefresh CI pipeline and reference integrations with issue-tracking and container registry tools for Codefresh to retrieve and enrich image information.
@@ -37,16 +37,16 @@ max-width="70%"
37
37
38
38
A set of dashboards provides visibility into all aspects of deployment:
39
39
40
-
* TheHome dashboard presents enterprise-wide deployment highlights across runtimes and clusters.
40
+
* TheGitOps Overview dashboard presents enterprise-wide deployment highlights across runtimes and clusters.
41
41
Get insights into important KPIs and deployments, all in the same location. View status of runtimes and managed clusters, deployments, failed deployments with rollbacks, most active applications. Use filters to narrow the scope to focus on anything specific.