kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/user/analytics/index.md

8 KiB
Raw Blame History

stage group info
Manage Optimize 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

Analytics (FREE)

Definitions

When we describe GitLab analytics, we use the following terms:

  • Cycle time: The duration of only the execution work alone. Often displayed in combination with "lead time," which is longer. GitLab measures cycle time from issue first merge request creation to issue close. This approach underestimates lead time because merge request creation is always later than commit time. GitLab displays cycle time in group-level Value Stream Analytics.

  • Deploys: The total number of successful deployments to production in the given time frame (across all applicable projects). GitLab displays deploys in group-level Value Stream Analytics.

  • DORA (DevOps Research and Assessment) "Four Keys":

    • Speed/Velocity

      • Deployment frequency: The average number of successful deployments to production per period. This effectively measures how often you are delivering value to end users. A higher deployment frequency means you are able to get feedback and iterate more quickly in delivering improvements and features faster. GitLab measures this as the number of deployments to a production environment in the given time period. GitLab displays deployment frequency in group-level Value Stream Analytics.
      • Lead Time for Changes: The time it takes for a commit to get into production. (1) GitLab measures this as the median duration between merge request merge and deployment to a production environment for all MRs deployed in the given time period. This measure under-estimates lead time because merge time is always later than commit time. The standard definition uses median commit time. We plan to start measuring from "issue first commit" as a better proxy, although still imperfect.

    • Stability

      • Change Failure Rate: The percentage of deployments causing a failure in production. GitLab measures this as the number of incidents divided by the number of deployments to a production environment in the given time period. This assumes:

        • All incidents are related to a production environment.
        • Incidents and deployments have a strictly one-to-one relationship (meaning any incident is related to only one production deployment, and any production deployment is related to no more than one incident).

      • Time to Restore Service: How long it takes an organization to recover from a failure in production. GitLab measures this as the average time required to close the incidents in the given time period. This assumes:

        • All incidents are related to a production environment.
        • Incidents and deployments have a strictly one-to-one relationship (meaning any incident is related to only one production deployment, and any production deployment is related to no more than one incident).

  • Lead time: The duration of your value stream, from start to finish. Different from Lead time for changes. Often displayed in combination with "cycle time," which is shorter. GitLab measures lead time from issue creation to issue close. GitLab displays lead time in group-level Value Stream Analytics.

  • MTTC (Mean Time to Change): The average duration between idea and delivery. GitLab measures MTTC from issue creation to the issue's latest related merge request's deployment to production.

  • MTTD (Mean Time to Detect): The average duration that a bug goes undetected in production. GitLab measures MTTD from deployment of bug to issue creation.

  • MTTM (Mean Time To Merge): The average lifespan of a merge request. GitLab measures MTTM from merge request creation to merge request merge (and closed/un-merged merge requests are excluded). For more information, see Merge Request Analytics.

  • MTTR (Mean Time to Recover/Repair/Resolution/Resolve/Restore): The average duration that a bug is not fixed in production. GitLab measures MTTR from deployment of bug to deployment of fix.

  • Throughput: The number of issues closed or merge requests merged (not closed) in some period of time. Often measured per sprint. GitLab displays merge request throughput in Merge Request Analytics.

  • Value Stream: The entire work process that is followed to deliver value to customers. For example, the DevOps lifecycle is a value stream that starts with "plan" and ends with "monitor". GitLab helps you track your value stream using Value Stream Analytics.

  • Velocity: The total issue burden completed in some period of time. The burden is usually measured in points or weight, often per sprint. For example, your velocity may be "30 points per sprint". GitLab measures velocity as the total points/weight of issues closed in a given period of time.

Lead time for changes

"Lead Time for Changes" differs from ordinary "Lead Time" because it "focuses on measuring only the time to deliver a feature once it has been developed", as described in (Measuring DevOps Performance).

Instance-level analytics

Introduced in GitLab 12.2.

Instance-level analytics make it possible to aggregate analytics across GitLab, so that users can view information across multiple projects and groups in one place.

Learn more about instance-level analytics.

Group-level analytics (PREMIUM)

  • Introduced in GitLab 12.8.
  • Moved to GitLab Premium in 13.9.

The following analytics features are available at the group level:

Project-level analytics

The following analytics features are available at the project level:

User-configurable analytics (ULTIMATE)

The following analytics features are available for users to create personalized views: