Stage Adoption Metrics

1. You are here:
2. Customer Success
3. Customer Success Management Handbook
4. Stage Adoption Metrics

On this page

• On this page
• Manage
• Plan
• Create
• Verify
• Package
• Secure
• Release
• Configure
• Monitor
• Govern

View the CSM Handbook homepage for additional CSM-related handbook pages.

---

2023-06-15 Note: The approach described below is no longer in active use. The Use Case Adoption Scoring page should be referenced for thresholds and information on the methodology CSMs use for measuring adoption of use cases.

As part of the CSM's mandate to drive stage adoption and expansion with customers, we need to define exactly what it means to adopt a stage at GitLab. For more information on how stage expansion is recorded and reported on, please visit this page The detail below is a guide to defining what it takes to say a customer has adopted that stage within GitLab. We define stage adoption as >25% of the account using a stage as defined below. Less than 25% (roughly) is presumed to be a pilot or work in progress toward a significant foothold of a stage providing value within the company.

Manage

Using 2 of the following:

• Using Code Analytics and Insights within GitLab.
• Using Value Stream Management within GitLab.

Usage Discovery Questions:

1. How do your admins monitor changes to user permission levels?
2. How do you keep track of which users have access to certain groups within GitLab?
3. How are you measuring developer cycle time?
4. How do you measure efficiencies within a group or project?

Plan

• Using Issue Tracking and/or Epics across 50% of teams.

Usage Discovery Questions:

1. What tools do you use to organize, plan and track project work?
2. Describe your issue and epic workflow.

Create

If there is no data currently being recorded for your customer in version.gitlab.com, you can ask whether they are:

• Using GitLab for git repo storage and code review (MR's).

Using data from version.gitlab.com and the Metrics Dictionary you can determine if the customer is doing the following:

• Using Merge Requests as part of the development lifecycle. (counts.merge_requests)
• Increase in projects with repositories with continuous growth over 3 months (counts.projects_with_repositories_enabled)
• Increase in source control pushes/commits with continuous growth over 3 months (counts.source_code_pushes)

Usage Discovery Questions:

1. Where do you manage your code base?
2. What processes do you follow for code reviews?

Verify

If there is no data currently being recorded for your customer in version.gitlab.com, you can ask whether they have:

• Made instance level shared Runner(s) available.
• More than 25% of teams or projects are using GitLab CI/CD.
• When 75+% of pipelines are using GitLab CI/CD.

Using data from version.gitlab.com and the Metrics Dictionary you can determine if the customer is doing the following:

• Made instance level shared Runner(s) available. (gitlab_shared_runners_enabled)
• Using Continuous Integration (CI) with continuous growth over 3 months (ci_internal_pipelines)
• Using CI Runners to build pipelines (counts.ci_builds)

Usage Discovery Questions:

1. What types of Runners are you using today? (shared, group, specific)
2. What tools are you using for continuous integration?

Package

• Using one or more of our registries (Package Registry, Container Registry, Helm Registry).

Usage Discovery Questions:

1. What tools do you use for package management?
2. What do you use to maintain Docker images?
3. Do you use the GitLab Container Registry to manage Helm Charts?

Secure

If there is no data currently being recorded for your customer in version.gitlab.com, you can ask whether they have:

• Using one of more of our security testing tools (SAST, DAST, Container Scanning, Dependency Scanning) with continuous growth over 3 months

Using data from version.gitlab.com and the Metrics Dictionary you can determine if the customer is doing the following:

• Using one of more of our security testing tools (SAST, DAST, Container Scanning, Dependency Scanning) with continuous growth over 3 months
• SAST jobs (counts.sast_jobs)
• DAST jobs (counts.dast_jobs)
• Dependency scanning jobs (counts.dependency_scanning_jobs)
• License management jobs (counts.license_management_jobs)
• Secret detection jobs (counts.secret_detection_jobs)
• Container scanning jobs - counts.container_scanning_jobs

Usage Discovery Questions:

1. What do you use to scan your application source code and binaries?
2. Do you analyze your running web application for known runtime vulnerabilities?
3. What do you use to check your Docker images for known vulnerabilities?
4. Do you look for known vulnerabilities in you external dependencies?

Release

• Using GitLab CI/CD to deploy their product (either the customer tells us this or we can see a high number of deployments and/or environments in the Usage Ping data).
• From a feature standpoint, if they are using 2 of the following features…
  • Pages
  • Review Apps
  • Feature Flags
  • Release Orchestration

Usage Discovery Questions:

1. Are you using GitLab to deploy your applications?
2. Do you use GitLab pages to create, manage and deploy static sites?
3. Are you making use of review apps to get a full production like environment in every merge request?
4. How do you currently manage your releases? (i.e. versioning, release notes, etc.)

Configure

• Using AutoDevOps, Kubernetes or Infrastructure As Code with 25% of teams or projects.

Usage Discovery Questions:

1. Are you using AutoDevOps to provide your users a pre-defined CI/CD configuration?
2. Are you using Kubernetes for any of the following scenarios?
3. Deploying software from GitLab CI/CD pipelines to Kubernetes
4. Using Kubernetes to manage runners attached to your GitLab instance
5. Running the GitLab application and services on a Kubernetes cluster

Monitor

• Using Prometheus & Grafana to monitor their GitLab server.
• Or using Prometheus to monitor 25% of their project deployments.

Usage Discovery Questions:

1. How are you monitoring the stability and performance of your GitLab instance?
2. What do you use to monitor your deployed applications?

Govern

• Vulnerability List
• Dependency List
• Security Policies
• Making use of Audit Events at the instance level as part of managing GitLab.
• Using Compliance Management within GitLab.

Usage Discovery Questions:

1. How do you manage HTTP traffic to your deployed application?
2. What do you use to block malicious traffic before it reaches your application?
3. How are you managing your Container Image for known vulnerabilities?
4. How are protecting your Kubernetes deployment for security threats at host / network level?