GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsGitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsNote: This page is dynamically generated via the Dev Section performance indicators .yml file.
Stage/Group | PI Type | PI | Health | SaaS / SM | Implementation Status |
---|---|---|---|---|---|
Dev | Section CMAU | Estimated & Recorded Sum of Dev Section SMAU | Okay | Both | Complete |
Manage, Manage:Optimize | SMAU, GMAU | MAU Viewing Analytics Features | Okay | Both | Complete |
Manage:Access | Paid GMAU | MAU Using Paid SAML | Okay | SaaS | Complete |
Manage:Compliance | Paid GMAU | MAU Viewing Compliance Features | Attention | Both | Complete |
Manage:Import | GMAU | MAU importing | Unknown | Both | Dashboard |
Plan, Plan:Project Management | SMAU, Paid GMAU | MAU Interacting With Issues | Okay | Both | Complete |
Plan:Product Planning | Paid GMAU | MAU creating Epics each Month | Okay | Both | Complete |
Create | SMAU | Unique users writing to a Git repository | Okay | Both | Complete |
Create:Source Code | GMAU | Unique users writing to a project Git repository | Okay | Both | Complete |
Create:Code Review | GMAU | Unique users using Merge Requests | Okay | Both | Complete |
Create:Gitaly | Other | Availability | Unknown | Both | Instrumentation |
Create:Editor | GMAU | Unique users committing via any web editor | Attention | Both | Complete |
Create:Ecosystem | GMAU | MAU of any integration | Unknown | Both | Instrumentation |
A sum of all SMAUs across the three stages in the Dev Section (Manage, Plan, and Create) for All users and Paid users.
SaaS/SM: Both
Target: Estimated CMAU growth 4% MoM; 2.73M by end of FY21Q4 for CMAU, 603K by end of FY21Q4 for Paid CMAU
Is Primary PI: true
Metric Name: issues, action_monthly_active_users_project_repo, analytics_unique_visits_for_any_target
Chart (Sisense↗)
Secondary Chart (Sisense↗)
Tertiary Chart (Sisense↗)
Health: Okay
Implementation Status: Complete
Focus This Month (March):
The number of unique users viewing any Analytics page.
SaaS/SM: Both
Target: 116050
Is Primary PI: true
Metric Name: analytics_total_unique_counts_monthly
Chart (Sisense↗)
Secondary Chart (Sisense↗)
Tertiary Chart (Sisense↗)
Health: Okay
Implementation Status: Complete
The number of unique users logging into GitLab using SAML SSO for Groups.
SaaS/SM: SaaS
Target: 30000. See https://gitlab.com/gitlab-com/Product/-/issues/1832 for further detail.
Is Primary PI: true
Metric Name: user_auth_by_provider (Group_SAML)
Chart (Sisense↗)
Health: Okay
Implementation Status: Complete
The number of unique users viewing Audit Events, Compliance Dashboard, or Credential Inventory.
SaaS/SM: Both
Target: TBD (expected [April 2021](https://gitlab.com/gitlab-org/manage/compliance/general/-/issues/13))
Is Primary PI: true
Metric Name: i_compliance_audit_events, g_compliance_audit_events, g_compliance_dashboard, i_compliance_credential_inventory, usage_data_g_compliance_dashboard, usage_data_a_compliance_audit_events_api
Chart (Sisense↗)
Secondary Chart (Sisense↗)
Tertiary Chart (Sisense↗)
Health: Attention
Q2 2021
.Q2 2021
.Q2 2021
. - Adding additional credentials to the credential inventory. Planned for Q3 2021
.Implementation Status: Complete
New and cumulative number of projects using compliance frameworks.
SaaS/SM: Both
Target: 1,030 total new projects in Q4 using compliance frameworks (SaaS and self-managed combined)
Metric Name: projects_with_compliance_framework
Chart (Sisense↗)
Health: Attention
13.8
.13.9
. This iteration is particularly important for the reason below.13.10
we expect compliance frameworks to fully support one of our most requested solutions, group compliance pipelines, as a required step to implement it, which we expect to drive even more adoption of compliance frameworks.Implementation Status: Complete
A monthly count of the unique number of users performing an import
SaaS/SM: Both
Target: TBD - See Health section below for details
Is Primary PI: true
Metric Name: unique_users_all_imports
Health: Unknown
13.9
. This feature will enable a much easier migration of an entire GitLab group from one instance to another.Implementation Status: Dashboard
13.9
.Share of projects created via import within 90 days of the namespace's creation.
SaaS/SM: Both
Target: TBD - See Health section below for details
Metric Name: TBD
Health: Unknown
13.9
. This feature will enable a much easier migration of an entire GitLab group from one instance to another.Implementation Status: Dashboard
13.6
.Number of unique users interacting with an issue (open, close, reopen, adjust label, adjust milestone, adjust weight, comment)
SaaS/SM: Both
Target: 484,510 for All, 148,176 for Paid
Is Primary PI: true
URL(s)
Metric Name: redis_hll_counters.issues_edit.issues_edit_total_unique_counts_monthly
Chart (Sisense↗)
Secondary Chart (Sisense↗)
Tertiary Chart (Sisense↗)
Health: Okay
Implementation Status: Complete
Lessons Learned (February):
Focus This Month (March):
The number of unique users creating Epics each month.
SaaS/SM: Both
Target: 3,900 Combined Unique Users for Self Managed and SaaS
Is Primary PI: true
Metric Name: epics
Chart (Sisense↗)
Tertiary Chart (Sisense↗)
Health: Okay
Implementation Status: Complete
The number of unique users interacting (create, view, reference) each month
SaaS/SM: Both
Target: TBD
Metric Name: TBD
Health: Unknown
Implementation Status: Dashboard
A monthly count of the number of requirements created.
SaaS/SM: Both
Target: 1000 by end of March 2021
URL(s)
Metric Name: requirements_created
Chart (Sisense↗)
Health: Okay
Implementation Status: Dashboard
A rolling count of the number of unique users who performed any Git write operation within the last 28 days.
SaaS/SM: Both
Target: Our target growth rate is 3% higher than the previous month for SMAU, and 4% for Paid SMAU.
Is Primary PI: true
URL(s)
Metric Name: action_monthly_active_users_project_repo
Chart (Sisense↗)
Secondary Chart (Sisense↗)
Tertiary Chart (Sisense↗)
Health: Okay
Implementation Status: Complete
A rolling count of the number of unique users who performed any Git write operation within the last 28 days
SaaS/SM: Both
Target: Our target growth rate is 3% higher than the previous month for SMAU, and 4% for Paid SMAU.
Is Primary PI: true
URL(s)
Metric Name: action_monthly_active_users_project_repo
Chart (Sisense↗)
Secondary Chart (Sisense↗)
Tertiary Chart (Sisense↗)
Health: Okay
Implementation Status: Complete
A rolling count of the number of unique users who approved any merge request within the last 28 days
Target: TBD
URL(s)
Health: Unknown
A rolling count of the number of unique users who had one or more push rejected by any push rule within the last 28 days
Target: TBD
URL(s)
Health: Unknown
This is defined as users who perform one or more of the following actions in a merge request - create, merge, or close a Merge Request.
SaaS/SM: Both
Target: Our target growth rate is 3% higher than the previous month for SMAU, and 4% for Paid SMAU.
Is Primary PI: true
URL(s)
Metric Name: merge_requests_users
Chart (Sisense↗)
Secondary Chart (Sisense↗)
Tertiary Chart (Sisense↗)
Health: Okay
Implementation Status: Complete
SaaS/SM: Both
Target: TBD - Primarily this metric is used for monitoring the relationship between SCM GMAU and Code Review GMAU to make sure it doesn't not fall out of alignment.
URL(s)
Metric Name: merge_requests_users
Chart (Sisense↗)
Secondary Chart (Sisense↗)
Health: Unknown
Implementation Status: Complete
This is defined as users who use [GitLab Workflow](https://marketplace.visualstudio.com/items?itemName=GitLab.gitlab-workflow) for VS Code and make at least one API request to a GitLab instance.
SaaS/SM: Both
Target: TBD
Health: Unknown
Implementation Status: Instrumentation
Percentage of time during which Gitaly is fully operational and providing service to users within SLO parameters. Availability is measured according by Apdex (latency) and error rate. Gitaly 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.
SaaS/SM: Both
Target: 99.95%, consistent with GitLab.com availability service level objectives
Is Primary PI: true
URL(s)
Metric Name: gitaly_apdex
Health: Unknown
Implementation Status: Instrumentation
Number of recorded GitLab instances with Gitaly Cluster enabled
SaaS/SM: Self-Managed
Target: TBD
URL(s)
Metric Name: gitaly_clusters
Chart (Sisense↗)
Health: Attention
Implementation Status: Complete
A rolling count of the number of unique users who performed a Git write operation to any respository using the Web IDE, Web Editor or Snippet within a stage in the last 28 days
SaaS/SM: Both
Target: 4% growth month over month for All
Is Primary PI: true
URL(s)
Metric Name: action_monthly_active_users_ide_edit
Chart (Sisense↗)
Secondary Chart (Sisense↗)
Tertiary Chart (Sisense↗)
Health: Attention
Implementation Status: Complete
A rolling count of the number of unique users who performed a Git write operation to any respository using the Web IDE, Web Editor or Snippet within a stage in the last 28 days - users grouped by editor used
SaaS/SM: Both
Target: TBD
URL(s)
Metric Name: action_monthly_active_users_web_ide_edit, action_monthly_active_users_sfe_edit, action_monthly_active_users_snippet_editor_edit
Chart (Sisense↗)
Health: Unknown
Implementation Status: Completed Dashboard
The total number of commits made via the Web IDE.
SaaS/SM: Both
Target: Maintain organic growth, 650K by end of Q1 2021
URL(s)
Metric Name: web_ide_commits
Chart (Sisense↗)
Health: Attention
Implementation Status: Complete
The number of new Snippets created each month.
SaaS/SM: Both
Target: 4% Growth month-over-month to 82k Snippets per Month by Q2 2021
URL(s)
Metric Name: snippets_change
Chart (Sisense↗)
Health: Attention
Implementation Status: Complete
Monthly unique users that have made at least one commit via the static site editor.
SaaS/SM: Both
Target: 150 AMAU by June 30, 2021
URL(s)
Metric Name: static_site_editor_create_commit
Secondary Chart (Sisense↗)
Health: Attention
Implementation Status: Complete
Monthly unique users that have viewed or edited a wiki
SaaS/SM: Both
Target: 10% higher than current month (SaaS and self-managed combined)
URL(s)
Metric Name: action_monthly_active_users_wiki_repo
Chart (Sisense↗)
Secondary Chart (Sisense↗)
Health: Okay
Implementation Status: Complete
Monthly Unique Users of any GitLab integration.
SaaS/SM: Both
Target: TBD
Is Primary PI: true
URL(s)
Metric Name: TBD
Health: Unknown
Implementation Status: Instrumentation
The total number of active project service integrations across all usage ping data (which includes GitLab.com)
SaaS/SM: Both
Target: Maintain flat adoption rate relative to overall GitLab growth
Metric Name: projects_asana_active, projects_assembla_active, projects_bamboo_active, projects_bugzilla_active, projects_buildkite_active, projects_campfire_active, projects_confluence_active, projects_custom_issue_tracker_active, projects_discord_active, projects_drone_ci_active, projects_emails_on_push_active, projects_external_wiki_active, projects_flowdock_active, projects_github_active, projects_gitlab_slack_application_active, projects_hangouts_chat_active, projects_hipchat_active, projects_irker_active, projects_jenkins_active, projects_jira_active, projects_jira_cloud_active, projects_jira_dvcs_cloud_active, projects_jira_dvcs_server_active, projects_jira_issuelist_active, projects_jira_server_active, projects_mattermost_active, projects_mattermost_slash_commands_active, projects_microsoft_teams_active, projects_packagist_active, projects_pipelines_email_active, projects_pivotaltracker_active, projects_prometheus_active, projects_pushover_active, projects_redmine_active, projects_slack_active, projects_slack_notifications_active, projects_slack_slash_active, projects_slack_slash_commands_active, projects_teamcity_active, projects_unify_circuit_active, projects_webex_teams_active
Chart (Sisense↗)
Health: Okay
Implementation Status: Dashboard
The total number of active project integrations that are being defined by a Group or Instance integration
SaaS/SM: Both
Target: Not defined
URL(s)
Metric Name: TBD
Health: Unknown
Implementation Status: Dashboard
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 |
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) |
section |
Optional | the product section (Ex: dev) as defined in sections.yml |
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 | indicates the (K)PI health and reasons as nested attributes. This should be updated monthly before Key Meetings by the DRI. |
health.level |
Optional | indicates a value between 0 and 3 (inclusive) to represent the health of the (K)PI. This should be updated monthly before Key Meetings by the DRI. |
health.reasons |
Optional | indicates the reasons behind the health level. This should be updated monthly before Key Meetings by the DRI. Should be an array (indented lines starting with dashes) even if you only have one reason. |
urls |
Optional | list of urls associated with the (K)PI. Should be an array (indented lines starting with dashes) even if you only have one url |
funnel |
Optional | indicates there is a handbook link for a description of the funnel for this PI. Should be a URL |
sisense_data |
Optional | allows a Sisense dashboard to be embeded as part of the (K)PI using chart, dashboard, and embed as neseted attributes. |
sisense_data.chart |
Optional | indicates the numeric Sisense chart/widget ID. For example: 9090628 |
sisense_data.dashboard |
Optional | indicates the numeric Sisense dashboard ID. For example: 634200 |
sisense_data.shared_dashboard |
Optional | indicates the numeric Sisense shared_dashboard ID. For example: 185b8e19-a99e-4718-9aba-96cc5d3ea88b |
sisense_data.embed |
Optional | indicates the Sisense embed version. For example: v2 |
sisense_data_secondary |
Optional | allows a second Sisense dashboard to be embeded. Same as sisense data |
sisense_data_secondary.chart |
Optional | Same as sisense_data.chart |
sisense_data_secondary.dashboard |
Optional | Same as sisense_data.dashboard |
sisense_data_secondary.shared_dashboard |
Optional | Same as sisense_data.shared_dashboard |
sisense_data_secondary.embed |
Optional | Same as sisense_data.embed |
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, Group PPI) |
product_analytics_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. |
implementation |
Optional | indicates the implementation status and reasons as nested attributes. This should be updated monthly before Key Meetings by the DRI. |
implementation.status |
Optional | indicates the Implementation Status status. This should be updated monthly before Key Meetings by the DRI. |
implementation.reasons |
Optional | indicates the reasons behind the implementation status. This should be updated monthly before Key Meetings by the DRI. Should be an array (indented lines starting with dashes) even if you only have one reason. |
lessons |
Optional | indicates lessons learned from a K(PI) as a nested attribute. This should be updated monthly before Key Meetings by the DRI. |
lessons.learned |
Optional | learned is an attribute that can be nested under lessons and indicates lessons learned from a K(PI). This should be updated monthly before Key Meetings by the DRI. Should be an array (indented lines starting with dashes) even if you only have one lesson learned |
monthly_focus |
Optional | indicates monthly focus goals from a K(PI) as a nested attribute. This should be updated monthly before Key Meetings by the DRI. |
monthly_focus.goals |
Optional | indicates monthly focus goals from a K(PI). This should be updated monthly before Key Meetings by the DRI. Should be an array (indented lines starting with dashes) even if you only have one goal |
metric_name |
Optional | indicates the name of the metric in Self-Managed implemenation. The SaaS representation of the Self-Managed implementation should use the same name. |
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 :