GitLab
A single application for the entire DevOps lifecycle
GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Remote Work Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management
GitLab
A single application for the entire DevOps lifecycle
GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Remote Work Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management
| KPI | Health | Status |
|---|---|---|
| Direct signup ARR growth rate | Unknown |
|
| Free to paid ARR growth rate | Unknown |
|
| Net Retention | Unknown |
|
| Gross Retention | Unknown |
|
| GitLab.com Paid Net Promoter Score (PNPS) | Problem |
|
| Average Stages per User (SpU) | Unknown |
|
| New hire location factor | Unknown |
|
| Category Maturity Achievement | Unknown |
|
| Refunds processed as % of orders | Unknown |
|
| Monthly Active Users (MAU) | Unknown |
|
| Stage Monthly Active Users (SMAU) | Unknown |
|
| Active Hosts | Unknown |
|
| Acquisition impact | Unknown |
|
(Direct signup ARR in the current period - direct signup revenue in the prior period)/direct signup revenue in the prior period
This KPI cannot be public.
URL(s)
Status: Unknown
(Free to paid signup ARR in the current period - free to paid signup revenue in the prior period) / free to paid signup ARR in the prior period
This KPI cannot be public.
URL(s)
Status: Unknown
This is a subset of an existing KPI. Please see the definition for the parent KPI.
Target: Our Target net retention rate is 180%.
This KPI cannot be public.
URL(s)
Status: Unknown
This is a subset of an existing KPI. Please see the definition for the parent KPI.
Target: Our Target gross retention rate is 90%.
This KPI cannot be public.
URL(s)
Status: Unknown
What is a good Net Promoter Score? Our baseline is GOOD but we are striving to get to EXCELLENT. This KPI is measured as the percentage of paid customer "promoters" minus the percentage of paid customer "detractors" from a Net Promoter Score survey. Currently GitLab.com SaaS customers only. This data is collected via Qualtrics email survey.
Target: Our Target PNPS is 40.
This KPI cannot be public.
URL(s)
Status: Problem
Stages per user is calculated by dividing Stage Monthly Active User (SMAU) by Monthly Active Users (MAU). Stages per User (SpU) is meant to capture the number of DevOps stages the average user is using on a monthly basis. We hope to add this metric to the stage maturity page, alongside number of contributions.
Target: Our Target SpU is 1.8.
Chart (Sisense↗)
Status: Unknown
This is a subset of an existing KPI. Please see the definition for the parent KPI.
Target: Our Target is 0.72.
Chart (Sisense↗)
Status: Unknown
Percentage of category maturity plan achieved per quarter
Target: Our Target is 70%.
This KPI cannot be public.
Status: Unknown
For a month take the number of refunds and divide that by the total amount of orders (including self-managed and sales initiated orders). More details available here
Chart (Sisense↗)
Status: Unknown
The number of unique users that performed an event within the previous 28 days.
Chart (Sisense↗)
Status: Unknown
Stage Monthly Active Users is a KPI that is required for all product stages. SMAU is defined as the specified AMAU within a stage in a 28 day rolling period.More details here
URL(s)
Chart (Sisense↗)
Status: Unknown
The count of active Self Hosts, Core and Paid, plus GitLab.com. This is measured by counting the number of unique GitLab instances that send us usage ping.
Chart (Sisense↗)
Status: Unknown
Acquisition impact measures the number of maturity levels advanced, as a result of acquisitions. The target is 3 per year.
Target: 3 per year
Status: Unknown
A count of events in which a package is published to or installed from the Package Registry on GitLab.com.
Target: Our FY21 Q2 target is a rolling 7-day average of 40k.
URL(s)
Chart (Sisense↗)
Status: Attention
Instrumentation: Attention
A rolling count of deployments with Gitlab in the last 30 days.
Target: Our FY21 Q2 target was to see an increase in deployments by at least 10%.
URL(s)
Chart (Sisense↗)
Status: Attention
Instrumentation: Okay
Percentage of time during which Gitaly is fully operational and providing service to users within SLO parameters. The availability of Gitaly is measured according to two metrics. Apdex, for latency and error rate, for errors. A service is considered available when at least 50% of users are experiencing satisfactory latency, _and_ 50% of requests are completing successfully. If either of these conditions is not met, the service is experiencing an outage.
Target: 99.95%
URL(s)
Status: Attention
Instrumentation: Attention
Proportion of users per each instance (self-managed) or userspace (GitLab.com) making use of Merge Requests. This is defined as users who perform one or more of the following actions in a merge request - create, comment, merge, or close a Merge Request.
Target: TBD
Status: Unknown
The total number of active project service integrations across all usage ping data (which includes GitLab.com)
Target: Not yet set
URL(s)
Chart (Sisense↗)
Status: Attention
The total number of commits made via the Web IDE.
Target: Unknown until we reach maturity level 2
URL(s)
Chart (Sisense↗)
Status: Problem
The number of new Snippets created each month.
Target: Unknown until we reach maturity level 2
URL(s)
Chart (Sisense↗)
Status: Problem
| Level | Meaning |
|---|---|
| Okay | The KPI is at an acceptable level compared to the threshold |
| Attention | This is a blip, or we’re going to watch it, or we just need to enact a proven intervention |
| Problem | We'll prioritize our efforts here |
| Unknown | Unknown |
| Level | Meaning |
|---|---|
| Okay | We are correctly capturing and measuring data for GitLab.com and self-managed instances. |
| Attention | Missing one of: GitLab.com or self-managed data. |
| Problem | Missing both: GitLab.com and self-managed data. |
| Unknown | Unknown |
Pages, such as the Engineering Function Performance Indicators page are rendered by an ERB template that contains HTML code.
Other PI Pages sectionmaturity table, make changes to the Performance Indicators Maturities ERB fileThese ERB templates calls custom helper functions that extract and transform data from the Performance Indicators data file.
kpi_list_by_org(org) helper function takes a required string argument named org (deparment or division level) that returns all the KPIs (pi.is_key == true) for a specific organization grouping (pi.org == org) from the Performance Indicators data file.pi_maturity_level(performance_indicator) helper function automatically assigns a maturity level based on the availability of certain data properties for a particular PI.pi_maturity_reasons(performance_indicator) helper function returns a reason for a PI maturity based on other data properties.performance_indicator_target(name) helper function returns the target value from the target property for a specific PI from the Performance Indicators data file.performance_indicators(org) takes a required string argument named org (deparment or division level) that returns two lists - a list of all KPIs and a list of all PIs for a specific organization grouping (department/division).signed_periscope_url(data) takes in the sisense_data property information from the Performance Indicators data file and returns a signed chart URL for embedding a Sisense chart into the handbook.The heart of pages like this is the Performance Indicators data file which is in YAML file. Each - denotes a dictionary of values for a new (K)PI. The current elements (or data properties) are:
| Property | Type | Description |
|---|---|---|
name |
Required | String value of the name of the (K)PI |
base_path |
Required | Relative path to the performance indicator page that this (K)PI should live on |
definition |
Required | refer to Parts of a KPI |
parent |
Optional | should be used when a (K)PI is a subset of another PI. For example, we might care about Hiring vs Plan at the company level. The child would be the division and department levels, which would have the parent flag. |
target |
Required | The target or cap for the (K)PI. Please use Unknown until we reach maturity level 2 if this is not yet defined. |
org |
Required | the organizational grouping (Ex: Engineering Function or Development Department) |
is_key |
Required | boolean value (true/false) that indicates if it is a (key) performance indicator |
health |
Required | has two additional elements/property - level (inclusive value between 0-3) and reasons. This should be updated monthly before Key Meetings by the DRI. |
urls |
Optional | list of urls associated with the (K)PI |
sisense_data |
Optional | contains elements/properties related to Sisense, including chart (numeric Sisense widget ID), dashboard (numeric Sisense dashboard ID), shared_dashboard (Sisense shared dashboard ID), embed (v2) |
public |
Optional | boolean flag that can be set to false where a (K)PI does not meet the public guidelines. |
instrumentation |
Optional | has two additional elements/property - level (inclusive value between 0-3) and reasons. This should be updated monthly before Key Meetings by the DRI. |
Here are some additional tips:
shared_dashboard, chart , and the dashboard key-value pairs to the Performance Indicators data file under the sisense_data property: in strings as it's an important character in YAML and will confuse the data parsing process. Put the string in "quotes" if you really need to use a :urls: should be an array (indented lines starting with dashes) even if you only have one urlmaturity.level and health.level display a value between 0 and 3 (inclusive). The health value is a manual input while the maturity is an automated value based on other discrete (K)PI data properties.
