2021-01-11 21:10:36 +00:00
---
stage: Release
group: Release
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# CI/CD Analytics
2021-01-28 06:08:59 +00:00
## Pipeline success and duration charts **(FREE)**
2021-01-11 21:10:36 +00:00
> - Introduced in GitLab 3.1.1 as Commit Stats, and later renamed to Pipeline Charts.
> - [Renamed](https://gitlab.com/gitlab-org/gitlab/-/issues/38318) to CI/CD Analytics in GitLab 12.8.
GitLab tracks the history of your pipeline successes and failures, as well as how long each pipeline
ran. To view this information, go to **Analytics > CI/CD Analytics** .
View successful pipelines:
![Successful pipelines ](img/pipelines_success_chart.png )
View pipeline duration history:
![Pipeline duration ](img/pipelines_duration_chart.png )
2021-03-16 15:11:17 +00:00
## DevOps Research and Assessment (DORA) key metrics **(ULTIMATE)**
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/275991) in GitLab 13.7.
> - Added support for [lead time for changes](https://gitlab.com/gitlab-org/gitlab/-/issues/291746) in GitLab 13.10.
2021-01-26 18:09:30 +00:00
Customer experience is a key metric. Users want to measure platform stability and other
post-deployment performance KPIs, and set targets for customer behavior, experience, and financial
impact. Tracking and measuring these indicators solves an important pain point. Similarly, creating
2021-01-27 00:08:53 +00:00
views that manage products, not projects or repositories, provides users with a more relevant data set.
2021-01-26 18:09:30 +00:00
Since GitLab is a tool for the entire DevOps life-cycle, information from different workflows is
integrated and can be used to measure the success of the teams.
The DevOps Research and Assessment ([DORA](https://cloud.google.com/blog/products/devops-sre/the-2019-accelerate-state-of-devops-elite-performance-productivity-and-scaling))
team developed four key metrics that the industry has widely adopted. You can use these metrics as
performance indicators for software development teams:
- Deployment frequency: How often an organization successfully releases to production.
- Lead time for changes: The amount of time it takes for code to reach production.
- Change failure rate: The percentage of deployments that cause a failure in production.
- Time to restore service: How long it takes an organization to recover from a failure in
production.
2021-03-16 15:11:17 +00:00
### Supported metrics in GitLab
The following table shows the supported metrics, at which level they are supported, and which GitLab version (API and UI) they were introduced:
| Metric | Level | API version | Chart (UI) version | Comments |
| --------------- | ----------- | --------------- | ---------- | ------- |
2021-05-18 18:10:54 +00:00
| `deployment_frequency` | Project-level | [13.7+ ](../../api/dora/metrics.md ) | [13.8+ ](#deployment-frequency-charts ) | The [old API endpoint ](../../api/dora4_project_analytics.md ) was [deprecated ](https://gitlab.com/gitlab-org/gitlab/-/issues/323713 ) in 13.10. |
2021-03-16 15:11:17 +00:00
| `deployment_frequency` | Group-level | [13.10+ ](../../api/dora/metrics.md ) | To be supported | |
2021-04-30 09:10:21 +00:00
| `lead_time_for_changes` | Project-level | [13.10+ ](../../api/dora/metrics.md ) | [13.11+ ](#lead-time-charts ) | Unit in seconds. Aggregation method is median. |
2021-03-16 15:11:17 +00:00
| `lead_time_for_changes` | Group-level | [13.10+ ](../../api/dora/metrics.md ) | To be supported | Unit in seconds. Aggregation method is median. |
| `change_failure_rate` | Project/Group-level | To be supported | To be supported | |
| `time_to_restore_service` | Project/Group-level | To be supported | To be supported | |
2021-01-26 18:09:30 +00:00
2021-04-12 18:12:15 +00:00
### Deployment frequency charts **(ULTIMATE)**
2021-01-11 21:10:36 +00:00
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/275991) in GitLab 13.8.
2021-04-30 09:10:21 +00:00
The **Analytics > CI/CD Analytics** page shows information about the deployment
frequency to the `production` environment. The environment must be part of the
[production deployment tier ](../../ci/environments/index.md#deployment-tier-of-environments )
for its deployment information to appear on the graphs.
2021-01-11 21:10:36 +00:00
2021-05-10 15:10:24 +00:00
![Deployment frequency ](img/deployment_frequency_charts_v13_12.png )
These charts are available for both groups and projects.
2021-04-12 18:12:15 +00:00
### Lead time charts **(ULTIMATE)**
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/250329) in GitLab 13.11.
The charts in the **Lead Time** tab show information about how long it takes
merge requests to be deployed to a production environment.
![Lead time ](img/lead_time_chart_v13_11.png )
Smaller values are better. Small lead times indicate fast, efficient deployment
processes.
For time periods in which no merge requests were deployed, the charts render a
red, dashed line.
2021-05-10 15:10:24 +00:00
These charts are only available for projects.