The section PI overview shows Primary PIs for each Product Section, Stage, and Group.
| Stage/Group | PI Type | PI | Health | SaaS / SM | PI Workflow |
|---|---|---|---|---|---|
| Enablement | Section PPI | Median End User Latency | Unknown | Both | |
| Enablement:Distribution | Group PPI | Percentage of installations on the 3 most recent versions of GitLab | Attention | Both | |
| Enablement:Geo | Paid GMAU | Number of unique users utilizing a Geo secondary | Unknown | Both | |
| Enablement:Memory | Group PPI | Requests / Compute | Unknown | Both | |
| Enablement:Global Search | Paid GMAU | The number of unique paid users per month | Unknown | Both | |
| Enablement:Database | Group PPI | Database Query Apdex (100ms target, 250ms tolerable) | Unknown | Both | |
| Enablement:Infrastructure | Paid GMAU | Number of unique paid users that perform an action on GitLab.com | Unknown | SaaS |
Median end user latency collected by Real User Monitoring. This metric captures how well we are doing in serving our primary customers, our end users, by measuring their end user experience.
Free/Paid: Both
SaaS/SM: Both
Target: TBD
Is Primary PI: true
URL(s)
Health: Unknown
Instrumentation: Problem
Of the total number of self-managed installs, what percentage are on one of the three most recent versions.
Free/Paid: Both
SaaS/SM: Both
Target: 40%
Is Primary PI: true
URL(s)
Chart (Sisense↗)
Health: Attention
Instrumentation: Attention
Number of unique users utilizing a Geo secondary. This adoption metric helps us understand whether end users are actually seeing value in, and are using, geo secondaries.
Free/Paid: Paid
SaaS/SM: Both
Target: TBD
Is Primary PI: true
URL(s)
Health: Unknown
Instrumentation: Problem
Requests per Hour (Rolling 7 day average) / Compute Cost. This metric is a measure of efficiency, measuring how many requests GitLab can service for one compute dollar. As GitLab is more efficient with CPU and Memory, it will go up.
Free/Paid: Both
SaaS/SM: Both
Target: TBD
Is Primary PI: true
URL(s)
Chart (Sisense↗)
Health: Unknown
Instrumentation: Problem
The number of unique active users interacting with either Basic Search or Advanced Search per Month.
Free/Paid: Both
SaaS/SM: Both
Target: TBD
Chart (Sisense↗)
Health: Unknown
Instrumentation: Problem
The number of unique paid users interacting with Advanced Search per month.
Free/Paid: Paid
SaaS/SM: Both
Target: TBD
Is Primary PI: true
Health: Unknown
Instrumentation: Problem
Database query Apdex, with 100ms the target and 250ms tolerable. This measures the ratio of queries which complete within the satisfactory time, informing how well the database is scaling and performing.
Free/Paid: Both
SaaS/SM: Both
Target: TBD
Is Primary PI: true
URL(s)
Health: Unknown
Instrumentation: Problem
The number of unique users that performed an action on gitlab.com in a 28 day rolling period.
Free/Paid: Both
SaaS/SM: SaaS
Target: TBD
Chart (Sisense↗)
Health: Unknown
Instrumentation: Attention
The sum of all monthly active users on gitlab.com that roll up to paid accounts in a 28 day rolling period.
Free/Paid: Paid
SaaS/SM: SaaS
Target: TBD
Is Primary PI: true
URL(s)
Health: Unknown
Instrumentation: Problem
| Value | Level | Meaning |
|---|---|---|
| 3 | Okay | The KPI is at an acceptable level compared to the threshold |
| 2 | Attention | This is a blip, or we’re going to watch it, or we just need to enact a proven intervention |
| 1 | Problem | We'll prioritize our efforts here |
| 0 | Unknown | Unknown |
| Value | Level | Meaning |
|---|---|---|
| 3 | Okay | We are correctly capturing and measuring data for GitLab.com and self-managed instances. |
| 2 | Attention | Missing one of: GitLab.com or self-managed data. |
| 1 | Problem | Missing both: GitLab.com and self-managed data. |
| 0 | Unknown | Unknown |
Pages, such as the Engineering Function Performance Indicators page are rendered by an ERB template that contains HTML code.
Other PI Pages sectionThese 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_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 Performance Indicators data files and returns a signed chart URL for embedding a Sisense chart into the handbook.The heart of pages like this are Performance Indicators data files which are YAML files. 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. For Product PIs, product hierarchy should be separate from name by " - " (Ex. {Stage Name}:{Group Name} - {PI Type} - {PI Name} |
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. For GMAU, the target should be quarterly. |
org |
Required | the organizational grouping (Ex: Engineering Function or Development Department). For Product Sections, ensure you have the word section (Ex : Dev Section) |
stage |
Optional | the product stage (Ex: release) as defined in stages.yml |
group |
Optional | the product group (Ex: progressive_delivery) as defined in stages.yml |
category |
Optional | the product group (Ex: feature_flags) as defined in categories.yml |
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) |
sisense_data_secondary |
Optional | same as sisense_data. Allows a second sisense chart to be included. |
public |
Optional | boolean flag that can be set to false where a (K)PI does not meet the public guidelines. |
pi_type |
Optional | indicates the Product PI type (Ex: AMAU, GMAU, SMAU) |
plan_type |
Optional | indicates if the metric is Free, Paid, or Both. |
telemetry_type |
Optional | indicates if the metric is available on SaaS, SM (self-managed), or Both. |
is_primary |
Optional | boolean flag that indicates if this is the Primary PI for the Product Group. |
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. |
pi_workflow |
Optional | indicates the PI Workflow status |
Above ...Below ...At ...At or above ...At or below ...shared_dashboard, chart , and the dashboard key-value pairs to the corresponding 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).