Understand how your teams adopt DevOps with DevOps reports

Orit Golowinski ·
Dec 15, 2021 · 5 min read

GitLab has an extraordinary range of features for a single application, providing an entire DevOps platform from portfolio planning all the way through to monitoring and service desk. As such, GitLab is uniquely positioned to deliver a complete picture of your organization's DevOps journey and your return on investment in automation and DevOps practices.

Some of the most interesting and difficult questions that organizations ask themselves are:


GitLab has several metrics to give you insight into the development lifecycle:

Some analytics are only available for instance-level (self-managed), group level, or project level. Read more about analytics.

These analytics are a great way to see contributions from different projects and groups. On their own, however, they don't give insights into which processes your teams are using. For that, we offer DevOps Reports.

DevOps adoption reports

DevOps Adoption is a DevOps Report located in group-level analytics. It shows you data for how teams in your organization use the most essential GitLab features.

You can use DevOps Adoption to:

DevOps Adoption

In this example, we can see some interesting data on how a team uses features in development, security, and operations categories:

In the future we plan to add even more feature categories to DevOps Reports, such as:

…and much more. You can follow our future plans in the following epic.

DevOps Reports are available for the Ultimate tier for self-managed and SaaS users. To find DevOps Reports, go to your group and in the left sidebar, select Analytics > DevOps adoption

DevOps Score

You can use the DevOps score to compare your DevOps status to other organizations.

The DevOps Score tab shows usage of major GitLab features on your instance over the last 30 days. GitLab calculates the averages feature usage based on the number of billable users in that time period. You can also see the Leader usage score, calculated from top-performing instances based on Service Ping data that GitLab collects. GitLab compares your score to the lead score of each feature and shows it as a percentage underneath the feature. Your overall DevOps Score is an average of your feature scores.

To analyze your DevOps Score, GitLab aggregates Service Ping (sometimes referred to as Usage Ping) data on GitLab servers for analysis. Your usage information is not sent to any other GitLab instances. If you have just started using GitLab, it may take a few weeks for GitLab to collect enough data to calculate your DevOps Score.

DevOps Score

DevOps score is available at the admin panel for all tiers under Analytics > DevOps Reports.

To see the DevOps score, you must activate your GitLab instance’s Service Ping. This is because DevOps Score is a comparative tool, so your score data must first be centrally processed by GitLab, Inc.

There are several benefits of enabling Service Ping, such as DevOps Score and cohorts:


Cohorts shows your teams' GitLab activities over time, and is a useful tool for administrators to view user retention and manage seats in their GitLab instance.


Users are considered active if they have performed at least one of the following activities:

Cover image credit:

Cover image by John Schnobrich on Unsplash

“Get an overview of your entire DevOps adoption from planning to monitoring.” – Orit Golowinski

Click to tweet

Guide to the Cloud

Harness the power of the cloud with microservices, cloud-agnostic DevOps, and workflow portability.

Learn more
Open in Web IDE View source