Analyze GitLab usage

History

GitLab provides different types of analytics insights for instances, groups, and projects.

Analytics features

End-to-end insight & visibility analytics

Use these features to gain insights into your overall software development lifecycle.

FeatureDescriptionProject-levelGroup-levelInstance-level
Value Streams DashboardInsights into DevSecOps trends, patterns, and opportunities for digital transformation improvements.check-circle Yescheck-circle Yesdotted-circle No
Value Stream Management AnalyticsInsights into time-to-value through customizable stages.check-circle Yescheck-circle Yesdotted-circle No
DevOps adoption by group and by instanceOrganization’s maturity in DevOps adoption, with feature adoption over time and feature distribution by group.dotted-circle Nocheck-circle Yescheck-circle Yes
Usage trendsOverview of instance data and changes in data volume over time.dotted-circle Nodotted-circle Nocheck-circle Yes
InsightsCustomizable reports to explore issues, merged merge requests, and triage hygiene.check-circle Yescheck-circle Yesdotted-circle No
Product analyticsUnderstanding how users behave and interact with your product.dotted-circle Nocheck-circle Yesdotted-circle No
Analytics dashboardsBuilt-in and customizable dashboards to visualize collected data.check-circle Yescheck-circle Yesdotted-circle No

Productivity analytics

Use these features to gain insights into the productivity of your team on issues and merge requests.

FeatureDescriptionProject-levelGroup-levelInstance-level
Issue analyticsVisualization of issues created each month.check-circle Yescheck-circle Yesdotted-circle No
Merge request analyticsOverview of merge requests, with mean time to merge, throughput, and activity details.check-circle Yesdotted-circle Nodotted-circle No
Productivity analyticsMerge request lifecycle, filterable down to author level.dotted-circle Nocheck-circle Yesdotted-circle No
Code review analyticsOpen merge requests with information about merge request activity.check-circle Yesdotted-circle Nodotted-circle No

Developer analytics

Use these features to gain insights into developer productivity and code coverage.

FeatureDescriptionProject-levelGroup-levelInstance-level
Contribution analyticsOverview of contribution events made by group members, with bar chart of push events, merge requests, and issues.dotted-circle Nocheck-circle Yesdotted-circle No
Contributor analyticsOverview of commits made by project members, with line chart of number of commits.check-circle Yesdotted-circle Nodotted-circle No
Repository analyticsProgramming languages used in the repository and code coverage statistics.check-circle Yescheck-circle Yesdotted-circle No

CI/CD analytics

Use these features to gain insights into CI/CD performance.

FeatureDescriptionProject-levelGroup-levelInstance-level
CI/CD analyticsPipeline duration and successes or failures.check-circle Yescheck-circle Yesdotted-circle No
DORA metricsDORA metrics over time.check-circle Yescheck-circle Yesdotted-circle No

Security analytics

Use these features to gain insights into security vulnerabilities and metrics.

FeatureDescriptionProject-levelGroup-levelInstance-level
Security DashboardsCollection of metrics, ratings, and charts for vulnerabilities detected by security scanners.check-circle Yescheck-circle Yesdotted-circle No

Glossary

The following glossary provides definitions for common development metrics used in analytics features, and explains how they are measured in GitLab.

MetricDefinitionMeasurement in GitLab
Mean Time to Change (MTTC)The average duration between idea and delivery.From when an issue is created until its related merge request is deployed to production.
Mean Time to Detect (MTTD)The average duration that a bug goes undetected in production.From when a bug is deployed to production until an issue is created to report it.
Mean Time to Merge (MTTM)The average lifespan of a merge request.From when a merge request is created until it is merged. Excludes merge requests that are closed or unmerged. For more information, see merge request analytics.
Mean Time to Recover / Repair / Resolution / Resolve / Restore (MTTR)The average duration that a bug is not fixed in production.From when a bug is deployed to production until the bug fix is deployed.
VelocityThe total issue burden completed in a specific period of time. The burden is usually measured in points or weight, often per sprint.Total points or weight of issues closed in a specific period of time. For example, “30 points per sprint”.