• Instance-level analytics
• Group-level analytics
• Project-level analytics
  • Remove project analytics from the left sidebar
• User-configurable analytics
• Value streams management
• Glossary

Analyze GitLab usage

Instance-level analytics

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.

For more information, see instance-level analytics.

Group-level analytics

GitLab provides several analytics features at the group level. Some of these features require you to use a higher tier than GitLab Free.

• Application Security
• Contribution
• DevOps Adoption
• Insights
• Issue
• Productivity
• Repositories
• Value Stream Management Analytics, and Value Stream Management Dashboard

Project-level analytics

You can use GitLab to review analytics at the project level. Some of these features require you to use a higher tier than GitLab Free.

• Analytics dashboards, enabled with the combined_analytics_dashboards_editor feature flag
• Application Security
• CI/CD & DORA
• Code Review
• Insights
• Issue
• Merge Request, enabled with the project_merge_request_analytics feature flag
• Repository
• Value Stream Management Analytics, and Value Stream Management Dashboard

Remove project analytics from the left sidebar

By default, analytics for a project are displayed under the Analyze item in the left sidebar. To remove this item:

1. On the left sidebar, at the top, select Search GitLab () to find your project.
2. Select Settings > General.
3. Expand Visibility, project features, permissions.
4. Turn off the Analytics toggle.
5. Select Save changes.

User-configurable analytics

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

• Application Security

Be sure to review the documentation page for this feature for GitLab tier requirements.

Value streams management

You can use the following analytics features to analyze and visualize the performance of your projects and groups:

• Value stream analytics for projects
• Value stream analytics for groups
• Value streams dashboard

Glossary

We use the following terms to describe GitLab analytics:

• Mean Time to Change (MTTC): 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.
• Mean Time to Detect (MTTD): The average duration that a bug goes undetected in production. GitLab measures MTTD from deployment of bug to issue creation.
• Mean Time To Merge (MTTM): 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.
• Mean Time to Recover/Repair/Resolution/Resolve/Restore (MTTR): The average duration that a bug is not fixed in production. GitLab measures MTTR from deployment of bug to deployment of fix.
• 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 or weight of issues closed in a given period of time.