Dev Section Performance Indicators

1. You are here:
2. Handbook
3. Product Handbook
4. Dev Section Performance Indicators

On this page

• Section PI Overview
• Regular Performance Indicators
  • Dev - Section TMAU - Recorded Sum of Dev Section SMAU
  • Manage, Manage:Optimize - SMAU, GMAU - MAU Viewing Analytics Features
  • Manage:Access - Paid GMAU - MAU Using Paid SAML
  • Manage:Compliance - Paid GMAU - MAU Viewing Compliance Features
  • Manage:Compliance - Other - Projects with Compliance Framework
  • Manage:Import - GMAU - MAU importing
  • Manage:Import - Other - Share of New Projects Imported
  • Plan, Plan:Project Management - SMAU, Paid GMAU - MAU Interacting With Issues
  • Plan:Product Planning - Paid GMAU - MAU creating Epics each Month
  • Plan:Certify - Paid GMAU - MAU Interacting with Requirements
  • Plan:Certify - Other - Number of Requirements Created Monthly
  • Create - SMAU - MAU Conducting Git Write Operations
  • Create:Gitaly - Other - Availability
  • Create:Gitaly - Other - Recorded Instances with Gitaly Cluster Enabled
  • Create:Source Code - GMAU - MAU Conducting Git Write Operations to project repository
  • Create:Code Review - GMAU - MAU using Merge Requests
  • Plan:Product Planning - Other - MAU that viewed or uploaded designs
  • Create:Editor - GMAU - MAU Conducting Git Write Operations from web editors
  • Create:Editor - Other - MAU Conducting Git Write Operation by editor
  • Create:Editor - Other - Number of Commits per Month from the Web IDE
  • Create:Editor - Other - Number of new Snippets per Month
  • Create:Editor - Other - MAU that committed via the SSE
  • Create:Editor - Other - MAU that viewed or edited a wiki
  • Create:Ecosystem - GMAU - MAU of any integration
  • Create:Ecosystem - Other - Total active project integrations
  • Create:Ecosystem - Other - Integrations managed at Group or Instance level
• Other PI Pages
• Legends
  • Health
• How to work with pages like this
  • Pages
    • Helper Functions
  • Data
  • Guidelines

Note: This page is dynamically generated via the Dev Section performance indicators .yml file.

Section PI Overview

Stage/Group	PI Type	PI	Health	SaaS / SM	Implementation Status
Dev	Section TMAU	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	Both	Complete
Manage:Compliance	Paid GMAU	MAU Viewing Compliance Features	Unknown	Both	Complete
Manage:Import	GMAU	MAU importing	Unknown	Both	Complete
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	MAU Conducting Git Write Operations	Okay	Both	Complete
Create:Gitaly	Other	Availability	Unknown	Both	Instrumentation
Create:Source Code	GMAU	MAU Conducting Git Write Operations to project repository	Okay	Both	Complete
Create:Code Review	GMAU	MAU using Merge Requests	Unknown	Both	Dashboard
Create:Editor	GMAU	MAU Conducting Git Write Operations from web editors	Unknown	Both	Complete
Create:Ecosystem	GMAU	MAU of any integration	Unknown	Both	Instrumentation

Regular Performance Indicators

Dev - Section TMAU - Recorded Sum of Dev Section SMAU

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 TMAU growth 4% MoM; 2.73M by end of FY21Q4 for TMAU, 603K by end of FY21Q4 for Paid TMAU

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

• Original targets of 1.25M/200K for TMAU/Paid TMAU based on recorded TMAU for FY21Q3 were achieved!
• Just now seeing Manage SMAU from self-managed instances; expect larger increases over the next few months.
• As expected, large jumps as people upgrade to 13.3 and beyond to properly report Create SMAU
• Plan SMAU data on this chart is ~23,000 users short due to it needing to be updated to the new calculation. Tracking via this issue
• Improvements - For All Usage, Address the problem areas that emerged out of the Category Maturity Scorecard exercise for Issue Tracking and continue making progress on quality of life improvements for existing Plan features.
• Improvements - For All Usage, Merge Request usability improvements
• Improvements - For All Usage, MR reviewers will make us more competitive with GitHub and should help with the lovability of assigning merge requests
• Improvements - For All Usage, Iterations in GitLab will make plan more usable for many Agile development teams
• Improvements - For Paid Usage, Iterations in GitLab will make plan more usable for many Agile development teams
• Improvements - For Paid Usage, Epic Swimlanes will allow for much better portfolio management via boards
• Improvements - For Paid Usage, SSO Group Sync which is targeted for FY3-2020 will greatly help user permission management on GitLab.com

Implementation Status: Complete

Manage, Manage:Optimize - SMAU, GMAU - MAU Viewing Analytics Features

The number of unique users viewing any Analytics page.

SaaS/SM: Both

Target: 40,150 per month (SaaS only). Self-managed target TBD.

Is Primary PI: true

Metric Name: analytics_total_unique_counts_monthly

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Okay

• Starting in October, self-managed data is coming in as a result of implementing usage ping in 13.5. Analytics feature adoption on self-managed instances is at 64% of the estimated uplift. Overall usage (SaaS and self-managed) is at 96% of target. For paid users, usage is at 91% of target.

Implementation Status: Complete

• Please see this issue to track dashboard updates

Manage:Access - Paid GMAU - MAU Using Paid SAML

The number of unique users logging into GitLab using SAML SSO for Groups.

SaaS/SM: Both

Target: 10% higher than current month (SaaS and self-managed combined)

Is Primary PI: true

Metric Name: user_auth_by_provider (max value)

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Okay

• Launching SSO group sync for GitLab.com MVC in 13.6
• Releasing OneLogin support for SCIM and SAML in 13.6

Implementation Status: Complete

• Defined, instrumentation in 13.4
• Charts show the max value of the user_auth_by_provider set.

Manage:Compliance - Paid GMAU - MAU Viewing Compliance Features

The number of unique users viewing Audit Events, Compliance Dashboard, or Credential Inventory.

SaaS/SM: Both

Target: 10% higher than current month (SaaS and self-managed combined)

Is Primary PI: true

Metric Name: i_compliance_audit_events, g_compliance_audit_events, g_compliance_dashboard, i_compliance_credential_inventory

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Unknown

• Add a Projects view to the Compliance Dashboard. Planned for Q3 2020.
• Improve PAT & SSH credential management (epic). Ongoing with expected epic completion in 13.8.
• Add additional credentials (epic) to the credential inventory. Planned for Q4 2020
• Improve discoverability of Compliance features. Planned for Q1 2021.

Implementation Status: Complete

Manage:Compliance - Other - Projects with Compliance Framework

New and cumulative number of projects using compliance frameworks.

SaaS/SM: SaaS

Target: 10% higher than current month (SaaS and self-managed combined)

Metric Name: projects_with_compliance_framework

Chart (Sisense↗)

Health: Unknown

• No target defined yet

Implementation Status: Target

• We're iterating on compliance framework labels to give them more utility and solve several standardization and enforcement problems for customers. Next iteration expected in 13.6.

Manage:Import - GMAU - MAU importing

A monthly count of the unique number of users performing an import.

SaaS/SM: Both

Target: TBD

Is Primary PI: true

Metric Name: projects_imported (max value)

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Unknown

• No target defined yet
• Improvement - To enable users to self-service GitLab migrations, the Import group is currently focused on starting to iterate toward the Complete solution for GitLab-to-GitLab migrations.
• Improvement - Continue to enhance the GitHub Importer with emphasis on supporting larger migrations.

Implementation Status: Complete

• Defined and instrumented in 13.5
• The charts take the max value of the projects_imported, which only takes into account the most important import actions. A new combined metric for all import actions is planned.

Manage:Import - Other - Share of New Projects Imported

Share of projects created via import within 90 days of the namespace's creation.

SaaS/SM: Both

Target: TBD

Metric Name: TBD

Chart (Sisense↗)

Health: Unknown

• No target defined yet
• Insight - The share of imported projects has been trending up in the last 6 months. This coincides with the targeted effort to increase the discoverability of the import feature and to significantly reduce the number of known bugs.
• Improvement - To enable users to self-service GitLab migrations, the Import group is currently focused on starting to iterate toward the Complete solution for GitLab-to-GitLab migrations.
• Improvement - Continue to enhance the GitHub Importer with emphasis on supporting larger migrations.

Implementation Status: Dashboard

• Instrumented for both GitLab.com and self-managed in 13.6

Plan, Plan:Project Management - SMAU, Paid GMAU - MAU Interacting With Issues

Number of unique users interacting with an issue (open, close, reopen, adjust label, adjust milestone, adjust weight, comment)

SaaS/SM: Both

Target: 437,490 for All, 101,835 for Paid

Is Primary PI: true

URL(s)

• https://about.gitlab.com/direction/plan/issue_tracking/
• https://app.periscopedata.com/app/gitlab/722212/Plan:-Project-Management-GMAU

Metric Name: issues

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Okay

• Result - Surpassed GMAU goal of 196k (and 200k benchmark) recorded Self-Managed + SaaS SMAU. Set a new target for Q4 inclusive of estimated self-managed uplift.
• Driver - Iterations, Epic Swimlanes, Roadmap enhancements, Epic Boards, and Plan feature parity between an Instance, Group, and Project should drive wider adoption for Plan - especially Paid SMAU - over the next 3-6 months.
• Improvement - For All, work towards addressing the problem areas that emerged out of the Category Maturity Scorecard exercise for Issue Tracking.
• Improvement - For All, continue making progress on quality of life improvements for existing features.
• Improvement - For Paid, continue high level progress on achieving feature parity between an Instance, Group, and Project, making issues more extensible,and continuing to make incremental progress on iterations.
• Improvement - For Paid, creating multi-level Epics spanning a Group hierarchy is clunky and non-intuitive. Improving this, along with making the Roadmap more interactive and intuitive would be a huge catalyst to drive Product Planning adoption.
• Improvement - For Paid, continue making incremental, iterative progress towards Plan's core JTBD as outlined in the Issue Tracking direction.
• Insight - In Sep and Oct, MAU growth within existing instances far outpaced attrition, which is a strong signal of sustainable, organic adoption. More analysis is needed to filter by tier and identify top paying customers with elevated attrition and/or growth.
• Insight - During Q3, SaaS Trial users that interacted with Plan increased from 17% to 33% (94%). This is a strong signal that Plan is becoming more of a key consideration during the initial sales cycles.
• Insight - Plan adoption by version has improved from 33% in 12.7 to 45% in 13.4 – which represents a net improvement in adoption of 36% over the last 10 releases.

Implementation Status: Complete

• Updating dashboard to combine both Paid / All usage.
• Implementation - Completed adding interaction events from self-managed which allows us to count unique users performing multiple actions within Issues.
• Implementation - Next we are working on enhancing current xMAU reporting to include aggregate distinc counts. We need to figure out how to gracefully transition to the new counter without perceived xMAU loss.

Plan:Product Planning - Paid GMAU - MAU creating Epics each Month

The number of unique users creating Epics each month.

SaaS/SM: Both

Target: 1,500 Unique Users for Self Managed and 1,200 Unique Users for SaaS

Is Primary PI: true

URL(s)

• https://gitlab.com/gitlab-data/analytics/-/issues/5280

Metric Name: epics

Chart (Sisense↗)

Health: Okay

• Insight - GMAU dipped slightly, but this is in line with the 2-3mo cycle we consistently see as larger customers tend to heavily plan quarterly. Overall monthly epic creation hit an all time high of +6200
• Improvement - Swimlanes will be a significant driver of MAU growth for Portfolio Management in the nearterm (n2m) - giving visibility to the feature on boards and adding additional value to better visualize your in-flight issues through swimlanes. Epic Boards should continue the trend into the end of FY21 by enabling Portfolio-level planning.

Implementation Status: Complete

• Dashboarding - we've instrumented core metrics but are looking to expand the MAU definition to include all epic usage, not just creation, for a more accurate GMAU metric

  Issue. 2020-09 update - we are identifying the additional instrumentation needed to accomplish this.

Plan:Certify - Paid GMAU - MAU Interacting with Requirements

The number of unique users interacting (create, view, reference) each month

SaaS/SM: Both

Target: TBD

Metric Name: TBD

Health: Unknown

• Note - Certify will no longer collapse under the Product Planning group. Therefore, we're still surfacing "Other" metrics to track Requirements Management growth and we will re-prioritize implementation of this metric.
• Dashboarding not implemented yet so health is a proxy of our Certify's "other" metric and adhnoc anlaysis. Tracking issue
• Improvement - UX improvements for Requirements Management based on completed research study, Requirement Import functionality, Upcoming Quality Management MVC

Implementation Status: Dashboard

• Dashboarding - Requirement Creation is instrumented is complete. Tracking issue for gmau dashboard here

Plan:Certify - Other - Number of Requirements Created Monthly

A monthly count of the number of requirements created.

SaaS/SM: Both

Target: 5000 by end of December 2020

URL(s)

• https://gitlab.com/gitlab-data/analytics/-/issues/5270

Metric Name: requirements_created

Chart (Sisense↗)

Health: Okay

• Insight - Requirement creation has decreased, which is expected as organizations create requriements and then transition to satisfying them. Added urgency of implementation of requirement interactions)
• Insight - Self-managed instances creating requirements grew ~26% from Aug to Sept.
• Insight - While instance adoption continued to grow, the number of requirements dropped back below 1,200. We are potentially reporting GitLab data in this graph, and Aug had a large number of customer facing demos that could account for the spike. Tracking issue here

Implementation Status: Dashboard

• Dashboarding - accurate instrumentation on Self Managed, still needs verification for SaaS - issue
• Dashboarding - update metrics collection to track interactions

Create - SMAU - MAU Conducting Git Write Operations

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 10% for Paid SMAU.

Is Primary PI: true

URL(s)

• https://app.periscopedata.com/app/gitlab/728380/WIP-Create-Stage-Dashboard
• https://gitlab.com/gitlab-org/gitlab/-/issues/234027

Metric Name: action_monthly_active_users_project_repo

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Okay

• Insight - Git write operations are performed by a large number of users. On GitLab.com, approximately 10% of users perform a Git write operation every month. For licensed self-managed instances, this number should be much higher.
• AMAU is being tracked per repository type, and which means that we are under counting slightly by using project repositories at the moment gitlab#234027. From GitLab 13.6 this should be resolved.

Implementation Status: Complete

• Enabled on GitLab.com
• Released for self-managed in GitLab 13.3

Create:Gitaly - Other - Availability

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)

• https://dashboards.gitlab.net/d/gitaly-main/gitaly-overview
• https://gitlab.com/gitlab-org/gitlab/-/issues/216683

Metric Name: gitaly_apdex

Health: Unknown

• Instrumentation for this metric started in 13.4 and will finish in 13.6. Expect to see initial data by the December PI review.

Implementation Status: Instrumentation

• Rolling 7 day metrics available in Grafana for GitLab.com. Current availability per Adpex is 99.98%.
• self-managed availability metrics are planned

Create:Gitaly - Other - Recorded Instances with Gitaly Cluster Enabled

Number of recorded GitLab instances with Gitaly Cluster enabled

SaaS/SM: Self-Managed

Target: TBD

URL(s)

• https://dashboards.gitlab.net/d/gitaly-main/gitaly-overview

Metric Name: gitaly_clusters

Chart (Sisense↗)

Health: Attention

• No target defined
• Improvement - introduce Variable Replication Factor and auto-reblancing within a cluster to enable more enterprise-level adoption.

Implementation Status: Complete

• Instrumentation for reporting on instances with Gitaly Cluster enabled was introduced in 13.0 with the GA of Gitaly Cluster.

Create:Source Code - GMAU - MAU Conducting Git Write Operations to project repository

A rolling count of the number of unique users who performed a Git write operation to a project repository within the last 28 days

SaaS/SM: Both

Target: Our FY21 Q3 Target is to exceed 1m unique users performing Git write operations. As instances upgrade to GitLab 13.3 with improved instrumentation, we intend to switch to growth rate target aligned with user growth rates.

Is Primary PI: true

URL(s)

• https://app.periscopedata.com/app/gitlab/728380/WIP-Create-Stage-Dashboard?widget=9520571&udv=0
• https://gitlab.com/gitlab-org/gitlab/-/issues/234027

Metric Name: action_monthly_active_users_project_repo

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Okay

• Insight - Git write operations are performed by a large number of users. On GitLab.com, approximately 10% of users perform a Git write operation every month. For licensed self-managed instances, this number should be much higher.
• AMAU is being tracked per repository type, and which means that we are under counting slightly by using project repositories at the moment gitlab#234027
• Improvement - work towards providing users more insights while navigating their code with Code Intelligence
• Improvement - work towards providing more control over managing repository size

Implementation Status: Complete

• Enabled on GitLab.com
• Released for self-managed in GitLab 13.3

Create:Code Review - GMAU - MAU using Merge Requests

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: Unknown until we reach maturity level 2

Is Primary PI: true

URL(s)

• https://app.periscopedata.com/app/gitlab/526749/Create---Code-Review-category-dashboard

Metric Name: merge_requests_users

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Unknown

• CHANGE - Previously, this metric was reported as a percentage or users in an instance using Merge Requests. This metric has changed to an absolute number (as of November 2020) of users which is more consistent with other reporting. We'll work to reset targets and baselines quickly while we continue to evaluate if this is the correct metric.
• Improvement - work towards enhancing the UX of Merge Requests
• Improvement - work towards better coordination of cross-stage changes to the Merge Requests UX
• Improvement - work towards making suggested changes lovable

Implementation Status: Dashboard

• Enabled on GitLab.com 2020-07-04
• Enabled for self-managed on GitLab 13.2
• Updating dashboards to for Paid / All breakouts

Plan:Product Planning - Other - MAU that viewed or uploaded designs

Monthly unique users that have viewed or uploaded designs

SaaS/SM: Both

Target: 10% higher than current month (SaaS and self-managed combined)

URL(s)

• https://gitlab.com/gitlab-org/gitlab/-/issues/234041
• https://gitlab.com/gitlab-data/analytics/-/issues/4761

Metric Name: action_monthly_active_users_design_management

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Problem

• Ongoing - Data has still not extracted our MAU from the dataset.
• Waiting on SM instrumentation as per this issue
• Instrumentation scheduled in 13.5 but may slip to 13.6 due to Group Level wiki
• No target defined yet

Implementation Status: Complete

• Removed WIP sisense chart as it was shoing actions, not users
• Have .com data for design views, reads, updates but not MAU
• Instrumenting usage ping and updates/creates for 13.5/13.6 - this pushed back due to holidays/parental leave

Create:Editor - GMAU - MAU Conducting Git Write Operations from web editors

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: 120K for All

Is Primary PI: true

URL(s)

• https://app.periscopedata.com/app/gitlab/741875/Create:Editor-xMAU

Metric Name: action_monthly_active_users_ide_edit

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Unknown

• Data collection is beginning, but it's too early to draw any insights as instances continue to upgrade and report data.

Implementation Status: Complete

• Instrumentation of the Web IDE is in place for both self-managed and SaaS.
• Instrumentation of Static Site Editor and Wiki to roll up into GMAU scheduled for 13.7
• New target GMAU to be set once we get cumulative, de-duped data from new categories

Create:Editor - Other - MAU Conducting Git Write Operation by editor

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)

• https://app.periscopedata.com/app/gitlab/741875/Create:Editor-xMAU

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

• Data collection is beginning, but it's too early to define a target as instances continue to upgrade and report data.
• Insight - Editing through the Web Editor (single file editor) is 3 to 1 for users of the Web IDE. This confirms data recognized previously based on navigation paths that the single file editor is more widely used. We need to continute monitoring this to determine future investments in the Web IDE.

Implementation Status: Dashboard

• Instrumentation is in place for both self-managed and SaaS.
• Updating dashboards to for Paid / All breakouts

Create:Editor - Other - Number of Commits per Month from the Web IDE

The total number of commits made via the Web IDE.

SaaS/SM: Both

Target: FLAT - Maintain 500k Commits per Month while we continue to see more trending data.

URL(s)

• https://gitlab.com/gitlab-data/analytics/-/issues/4398
• https://gitlab.com/gitlab-data/analytics/-/issues/6149

Metric Name: web_ide_commits

Chart (Sisense↗)

Health: Okay

• Insight - Commit count remains steady with a general trend upward.
• Insight - New CI Authoring group may have conflicting path for continuing to drive usage to Web IDE.

Implementation Status: Complete

• Instrumentation working and charts updated to include both self-managed and SaaS data.
• Updating dashboard for Paid / All breakout.

Create:Editor - Other - Number of new Snippets per Month

The number of new Snippets created each month.

SaaS/SM: Both

Target: 10% Growth to ~73k Snippets per Month

URL(s)

• https://gitlab.com/gitlab-data/analytics/-/issues/4400

Metric Name: snippets_change

Chart (Sisense↗)

Health: Okay

• Inisght - Overall decline in Snippets for August compared to July, but usage remains consistent.
• Improvement - Snippets with Multiple Files was released in GitLab 13.5 which should continue to drive adoption and value as users upgrade and discover the feature.

Implementation Status: Complete

• Instrumentation for number of snippets is complete for self-managed and SaaS.

Create:Editor - Other - MAU that committed via the SSE

Monthly unique users that have made at least one commit via the static site editor.

SaaS/SM: Both

Target: 110 MAU by December 30, 2020

URL(s)

• https://app.periscopedata.com/app/gitlab/684213/WIP-Static-Site-Editor-Usage-Metrics
• https://about.gitlab.com/direction/create/static_site_editor/

Metric Name: static_site_editor_create_commit

Secondary Chart (Sisense↗)

Health: Attention

• Goal - drive early adoption, with a focus on internal GitLab team members editing the Handbook
• Insight - MAU continues flat while AMAU almost doubled, indicating those who are using the editor are find it increasingly valuable.
• Improvement - 13.6 added the MR Title and Description when submitting changes from the Static Site Editor
• Improvement - Address issues reported from Handbook editors that block full-time adoption in 13.7

Implementation Status: Instrumentation

• Usage Ping data available for sessions but not commits.
• Improvement - Instrumenting for Usage Ping in 13.6

Create:Editor - Other - MAU that viewed or edited a wiki

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)

• https://gitlab.com/gitlab-org/gitlab/-/issues/230481

Metric Name: action_monthly_active_users_wiki_repo

Chart (Sisense↗)

Secondary Chart (Sisense↗)

Health: Unknown

• Added this as a GMAU as of October so behind on this PI
• Changed this from git writes to views and edits
• Instrumentation scheduled in 13.5 but may slip to 13.6 due to Group Level wiki
• No target defined.

Implementation Status: Complete

• Scheduled for self-managed in GitLab 13.5
• Will need Group Level Data after 13.6
• Waiting to confirm data is available before building dashboard

Create:Ecosystem - GMAU - MAU of any integration

Monthly Unique Users of any GitLab integration.

SaaS/SM: Both

Target: TBD

Is Primary PI: true

URL(s)

• https://gitlab.com/gitlab-org/gitlab/-/issues/225678
• https://gitlab.com/gitlab-data/analytics/-/issues/5850

Metric Name: TBD

Health: Unknown

• No target defined
• Improvement - Adding Group and Instance integration will allow larger sets of projects to be integrated easily
• Improvement - Improvements and new functionality in the Jira integration should increase adoption, expanding on the success of our most popular integration

Implementation Status: Instrumentation

• Awaiting implementation of data in Usage Ping
• Awaiting implementation of Sisense dashboard (blocked by Usage Ping implementation)

Create:Ecosystem - Other - Total active project integrations

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

• Observation - Growth tracks fairly evenly against overall usage growth (total number of projects created), demonstrating flat relative adoption rate of integrations
• Observation - GitLab.com users integrate at ~1/3 the rate that self-managed users do

Implementation Status: Dashboard

• Good overall tracking of project integrations, detailed breakdown available per-integration
• Updating dashboards to for Paid / All breakouts

Create:Ecosystem - Other - Integrations managed at Group or Instance level

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)

• https://gitlab.com/gitlab-org/gitlab/-/issues/204802#note_392267011
• https://gitlab.com/gitlab-data/analytics/-/issues/5849

Metric Name: TBD

Health: Unknown

• No data so far

Implementation Status: Dashboard

• Usage ping recently implemented, no Dashboard yet

Other PI Pages

• Performance Indicator Maturity Table
• Engineering Function Performance Indicators
  • Customer Support Department Performance Indicators
  • Development Department Performance Indicators
    • Dev Sub-Department Performance Indicators
    • Ops Sub-Department Performance Indicators
    • Secure Sub-Department Performance Indicators
    • Threat Management Sub-Department Performance Indicators
    • Growth Sub-Department Performance Indicators
    • Enablement Sub-Department Performance Indicators
  • Infrastructure Department Performance Indicators
  • Quality Department Performance Indicators
  • Security Department Performance Indicators
  • UX Department Performance Indicators
• Product Performance Indicators
  • Dev Section Performance Indicators
  • Ops Section Performance Indicators
  • Sec Section Performance Indicators
  • Enablement Section Performance Indicators
  • Stage and Group Performance Indicators
• Corporate Finance Performance Indicators
• Recruiting Performance Indicators
• People Success Indicators
• Data Team KPI Index

Legends

Health

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

How to work with pages like this

Pages

Pages, such as the Engineering Function Performance Indicators page are rendered by an ERB template that contains HTML code.

• Any changes to the Performance Indicator (PI) ERB template will cascade to all links under the Other PI Pages section
• To add, delete, or update (K)PI information (including title, description, etc), make changes to the corresponding Performance Indicators data file. See more details in the Data section below.
• To update the way each individual (K)PI displays:
  • make changes to the Performance Indicators List ERB file for how the (K)PI is displayed on the KPI Index page
  • make changes to the Performance Indicators ERB file for any other properties and its format
• When adding a new PI page,
  • create the new PI page in the business division's handbook section (like the Engineering Division page)
  • include the relative link to the PI page in the Performance Indicators List ERB file
  • add all the (K)PI information into the corresponding Performance Indicators data file

Helper Functions

These ERB templates calls custom helper functions that extract and transform data from the Performance Indicators data file.

• The 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.
• The pi_maturity_level(performance_indicator) helper function automatically assigns a maturity level based on the availability of certain data properties for a particular PI.
• The pi_maturity_reasons(performance_indicator) helper function returns a reason for a PI maturity based on other data properties.
• The 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).
• The 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.

Data

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	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.

Guidelines

• Each KPI chart should be a timeseries chart.
  • Use Purple bars to denote values.
  • Use a Red stepped-line for timeseries target.
  • Directional targets will be used:
    • Above ...
    • Below ...
    • At ...
    • At or above ...
    • At or below ...
  • Optional: Use a single Green bar for the current month (in progress). Preferred for metrics which accumulate through a month but optional due to the performance impact to render the chart.
  • Optional: Use a Black line for rolling average.
• Each KPI should have a standalone dashboard with a single chart representing the KPI and a text box with a link back to the handbook definition.
  • In Sisense, create a shared dashboard link to get the shared dashboard ID.
  • In Sisense, use the Share Link action of the chart to get the chart (widget_id) and the dashboard ID.
  • Add the shared_dashboard, chart , and the dashboard key-value pairs to the corresponding Performance Indicators data file under the sisense_data property
• Multi-series performance indicators should consider the following guidelines:
  • If series are mutually exclusive, use stacked bars for each series with a monthly time series
  • If series are not mutually exclusive, use grouped bars for each series with a monthly time series
  • Do not graph any targets in the chart.
  • Current month styling guidelines will not apply
• Avoid : 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 :