diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-20 12:55:51 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-20 12:55:51 +0300 |
| commit | e8d2c2579383897a1dd7f9debd359abe8ae8373d (patch) | |
| tree | c42be41678c2586d49a75cabce89322082698334 /doc/development/usage_ping | |
| parent | fc845b37ec3a90aaa719975f607740c22ba6a113 (diff) | |
Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42
Diffstat (limited to 'doc/development/usage_ping')
| -rw-r--r-- | doc/development/usage_ping/dictionary.md | 4258 | ||||
| -rw-r--r-- | doc/development/usage_ping/index.md | 1580 | ||||
| -rw-r--r-- | doc/development/usage_ping/metrics_dictionary.md | 238 | ||||
| -rw-r--r-- | doc/development/usage_ping/metrics_instrumentation.md | 103 | ||||
| -rw-r--r-- | doc/development/usage_ping/product_intelligence_review.md | 92 | ||||
| -rw-r--r-- | doc/development/usage_ping/review_guidelines.md | 9 |
6 files changed, 4027 insertions, 2253 deletions
diff --git a/doc/development/usage_ping/dictionary.md b/doc/development/usage_ping/dictionary.md index e76fb302b9c..934bdf9c808 100644 --- a/doc/development/usage_ping/dictionary.md +++ b/doc/development/usage_ping/dictionary.md @@ -42,6 +42,8 @@ The number of active users existing in the instance. This is named the instance_ Group: `group::product intelligence` +Data Category: `Subscription` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -54,6 +56,8 @@ Unique visitors to any analytics feature by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -66,6 +70,8 @@ Unique visitors to any analytics feature by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -78,6 +84,8 @@ Unique visitors to /groups/:group/-/contribution_analytics Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -90,6 +98,8 @@ Unique visitors to /groups/:group/-/insights Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -102,6 +112,8 @@ Unique visitors to /groups/:group/-/issues_analytics Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -114,6 +126,8 @@ Unique visitors to /groups/:group/-/analytics/merge_request_analytics Group: `group::optimize` +Data Category: `Optional` + Status: `removed` Tiers: `free` @@ -126,6 +140,8 @@ Unique visitors to /groups/:group/-/analytics/productivity_analytics Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -138,6 +154,8 @@ Unique visitors to /groups/:group/-/analytics/value_stream_analytics Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -150,6 +168,8 @@ Unique visitors to /-/instance_statistics/cohorts Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -162,6 +182,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -174,6 +196,8 @@ Unique visitors to /-/instance_statistics/dev_ops_score Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -186,6 +210,8 @@ Unique visitors to/admin/usage_trends Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -198,6 +224,8 @@ Unique visitors to /:group/:project/-/analytics/code_reviews Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -210,6 +238,8 @@ Unique visitors to /:group/:project/insights Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -222,6 +252,8 @@ Unique visitors to /:group/:project/-/analytics/issues_analytics Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -234,6 +266,8 @@ Unique visitors to /:group/:project/-/analytics/merge_request_analytics Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -246,6 +280,8 @@ Unique visitors to /:group/:project/pipelines/charts Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -258,6 +294,8 @@ Unique visitors to /:group/:project/-/graphs/master/charts Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -270,6 +308,8 @@ Unique visitors to /:group/:project/-/value_stream_analytics Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -282,93 +322,109 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `compliance_unique_visits.a_compliance_audit_events_api` -Missing description +Unique users that have used the Audit Events API. -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216183912_a_compliance_audit_events_api.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216183912_a_compliance_audit_events_api.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `compliance_unique_visits.compliance_unique_visits_for_any_target` -Missing description +Number of unique visits to any compliance page -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216183914_compliance_unique_visits_for_any_target.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216183914_compliance_unique_visits_for_any_target.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `compliance_unique_visits.compliance_unique_visits_for_any_target_monthly` -Missing description +Number of unique visits to any compliance page over a given month -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183916_compliance_unique_visits_for_any_target_monthly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210216183916_compliance_unique_visits_for_any_target_monthly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `compliance_unique_visits.g_compliance_audit_events` -Missing description +Unique users who have viewed audit events -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216183906_g_compliance_audit_events.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216183906_g_compliance_audit_events.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `compliance_unique_visits.g_compliance_dashboard` -Missing description +Number of unique visitors to the compliance dashboard. -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216183904_g_compliance_dashboard.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216183904_g_compliance_dashboard.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `compliance_unique_visits.i_compliance_audit_events` -Missing description +Unique users that have viewed the instance-level audit events screen -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216183908_i_compliance_audit_events.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216183908_i_compliance_audit_events.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `compliance_unique_visits.i_compliance_credential_inventory` -Missing description +Unique users who have viewed the credential inventory -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216183910_i_compliance_credential_inventory.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216183910_i_compliance_credential_inventory.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `ultimate` ### `container_registry_enabled` @@ -378,6 +434,8 @@ A count of projects where the container registry is enabled Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -390,6 +448,8 @@ Identifies if a user is using an external container registry and what type Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -402,6 +462,8 @@ Identifies the version of the external registry being used Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -412,7 +474,9 @@ Count of issues created by the alert bot automatically [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180449_alert_bot_incident_issues.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` @@ -426,6 +490,8 @@ Total Searches for All Basic Search and Advanced Search in self-managed and SaaS Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -438,6 +504,8 @@ Count of API Fuzzing `docker-in-docker` jobs run by job name Group: `group::fuzz testing` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -450,6 +518,8 @@ Count of API Fuzzing jobs run by job name Group: `group::fuzz testing` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -462,6 +532,8 @@ Count of assignee lists created on Boards Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -474,6 +546,8 @@ Projects with Auto DevOps template disabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -486,6 +560,8 @@ Projects with Auto DevOps template enabled (excluding implicit Auto DevOps enabl Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -498,6 +574,8 @@ Count of Boards created Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -510,6 +588,8 @@ Unique builds in project Group: `group::pipeline execution` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -522,6 +602,8 @@ Total pipelines in external repositories Group: `group::pipeline execution` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -534,6 +616,8 @@ Total pipelines in GitLab repositories Group: `group::pipeline execution` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -546,6 +630,8 @@ Total pipelines from an Auto DevOps template Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -558,6 +644,8 @@ Total Pipelines from templates in repository Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -570,102 +658,120 @@ Pipeline schedules in GitLab Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts.ci_runners` -Total configured Runners in project +Total configured Runners of all types [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216175520_ci_runners.yml) Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts.ci_runners_group_type_active` -Total active instance Runners +Total active Group Runners [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210502050341_ci_runners_group_type_active.yml) Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts.ci_runners_group_type_active_online` -Total active and online group Runners +Total active and online Group Runners [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210502051922_ci_runners_group_type_active_online.yml) Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts.ci_runners_instance_type_active` -Total active group Runners +Total active Shared (Instance) Runners [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210502045402_ci_runners_instance_type_active.yml) Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts.ci_runners_instance_type_active_online` -Total active and online instance Runners +Total active and online Shared (Instance) Runners [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210502051651_ci_runners_instance_type_active_online.yml) Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts.ci_runners_online` -Total online Runners +Total online Runners of all types [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210502050942_ci_runners_online.yml) Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts.ci_runners_project_type_active` -Total active project Runners +Total active Specific (Project) Runners [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210502050834_ci_runners_project_type_active.yml) Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts.ci_runners_project_type_active_online` -Total active and online project Runners +Total active and online Specific (Project) Runners [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210502052036_ci_runners_project_type_active_online.yml) Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -678,6 +784,8 @@ Total configured Triggers in project Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -690,6 +798,8 @@ Total GitLab Managed clusters both enabled and disabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -702,6 +812,8 @@ Total GitLab Managed clusters with GitLab Managed App:Cert Manager installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -714,6 +826,8 @@ Total GitLab Managed clusters with GitLab Managed App:Cilium installed Group: `group::configure` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -726,6 +840,8 @@ Total GitLab Managed clusters with GitLab Managed App:Crossplane installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -738,6 +854,8 @@ Total GitLab Managed clusters with GitLab Managed App:Elastic Stack installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -750,6 +868,8 @@ Total GitLab Managed clusters with GitLab Managed App:Helm enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -762,6 +882,8 @@ Total GitLab Managed clusters with GitLab Managed App:Ingress installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -774,6 +896,8 @@ Total GitLab Managed clusters with GitLab Managed App:Jupyter installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -786,6 +910,8 @@ Total GitLab Managed clusters with GitLab Managed App:Knative installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -798,6 +924,8 @@ Total GitLab Managed clusters with GitLab Managed App:Prometheus installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -810,6 +938,8 @@ Total GitLab Managed clusters with GitLab Managed App:Runner installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -822,6 +952,8 @@ Number of Kubernetes clusters attached to GitLab currently disabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -834,6 +966,8 @@ Number of Kubernetes clusters attached to GitLab currently enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -846,6 +980,8 @@ Total GitLab Managed clusters with defined cluster management project Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -858,6 +994,8 @@ Total GitLab Managed clusters provisioned with GitLab on AWS EKS Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -870,6 +1008,8 @@ Total GitLab Managed clusters provisioned with GitLab on GCE GKE Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -882,6 +1022,8 @@ Total GitLab Managed clusters that are user provisioned Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -894,6 +1036,8 @@ Count of total unique commit comments. Does not include MR diff comments Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -906,6 +1050,8 @@ Count of confidential epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -918,6 +1064,8 @@ Count of Container Scanning jobs run Group: `group::container security` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -930,6 +1078,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -942,6 +1092,8 @@ Total visits to VSA (both group- and project-level) all time Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -954,6 +1106,8 @@ Count of DAST jobs run Group: `group::dynamic analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -966,6 +1120,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -978,6 +1134,8 @@ Count to Dependency List page views Group: `group::composition analysis` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -990,6 +1148,8 @@ Count of Dependency Scanning jobs run Group: `group::composition analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -1002,6 +1162,8 @@ Missing description Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -1014,6 +1176,8 @@ Total deployments count Group: `group::ops release` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1026,6 +1190,8 @@ Number of designs that were created Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1038,6 +1204,8 @@ Number of designs that were deleted Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1050,6 +1218,8 @@ Number of updates to designs Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1062,6 +1232,8 @@ Total available and stopped environments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -1074,6 +1246,8 @@ Count of issues that are assigned to an epic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -1086,6 +1260,8 @@ Count of all epics Group: `group::product planning` +Data Category: `Operational` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -1098,6 +1274,8 @@ Count of the deepest relationship level for epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -1110,6 +1288,8 @@ Total failed deployments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -1122,6 +1302,8 @@ Number of feature flag toggles Group: `group::progressive delivery` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -1134,6 +1316,8 @@ Number of replication events on a Geo primary Group: `group::geo` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -1146,6 +1330,8 @@ Total number of sites in a Geo deployment Group: `group::geo` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -1158,6 +1344,8 @@ Total Grafana integrations attached to projects Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -1170,6 +1358,8 @@ Total GitLab Managed disabled clusters previously attached to groups Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1182,6 +1372,8 @@ Total GitLab Managed clusters attached to groups Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1194,6 +1386,8 @@ Total count of groups as of usage ping snapshot Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1206,6 +1400,8 @@ Count of groups with active integrations for Asana Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1218,6 +1414,8 @@ Count of groups with active integrations for Assembla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1230,6 +1428,8 @@ Count of groups with active integrations for Bamboo CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1242,6 +1442,8 @@ Count of groups with active integrations for Bugzilla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1254,6 +1456,8 @@ Count of groups with active integrations for Buildkite Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1266,6 +1470,8 @@ Count of groups with active integrations for Campfire Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1278,6 +1484,8 @@ Count of groups with active integrations for Confluence Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1290,6 +1498,8 @@ Count of groups with active integrations for a Custom Issue Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1302,6 +1512,8 @@ Count of groups with active integrations for Datadog Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1314,6 +1526,8 @@ Count of groups with active integrations for Discord Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1326,6 +1540,8 @@ Count of groups with active integrations for Drone CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1338,6 +1554,8 @@ Count of groups with active integrations for Emails on Push Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1350,6 +1568,8 @@ Count of groups with active integrations for EWM Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1362,6 +1582,8 @@ Count of groups with active integrations for External Wiki Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1374,6 +1596,8 @@ Count of groups with active integrations for Flowdock Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1386,6 +1610,8 @@ Count of groups with active integrations for GitHub Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -1398,6 +1624,8 @@ Count of groups with active integrations for Hangouts Chat Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1410,6 +1638,8 @@ Count of groups with active integrations for HipChat Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -1422,6 +1652,8 @@ Count of active groups inheriting integrations for Asana Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1434,6 +1666,8 @@ Count of active groups inheriting integrations for Assembla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1446,6 +1680,8 @@ Count of active groups inheriting integrations for Bamboo CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1458,6 +1694,8 @@ Count of active groups inheriting integrations for Bugzilla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1470,6 +1708,8 @@ Count of active groups inheriting integrations for Buildkite Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1482,6 +1722,8 @@ Count of active groups inheriting integrations for Campfire Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1494,6 +1736,8 @@ Count of active groups inheriting integrations for Confluence Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1506,6 +1750,8 @@ Count of active groups inheriting integrations for a Custom Issue Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1518,6 +1764,8 @@ Count of active groups inheriting integrations for Datadog Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1530,6 +1778,8 @@ Count of active groups inheriting integrations for Discord Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1542,6 +1792,8 @@ Count of active groups inheriting integrations for Drone CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1554,6 +1806,8 @@ Count of active groups inheriting integrations for Emails on Push Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1566,6 +1820,8 @@ Count of active groups inheriting integrations for EWM Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1578,6 +1834,8 @@ Count of active groups inheriting integrations for External Wiki Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1590,6 +1848,8 @@ Count of active groups inheriting integrations for Flowdock Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1602,6 +1862,8 @@ Count of active groups inheriting integrations for GitHub Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -1614,6 +1876,8 @@ Count of active groups inheriting integrations for Hangouts Chat Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1626,6 +1890,8 @@ Count of active groups inheriting integrations for HipChat Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -1638,6 +1904,8 @@ Count of active groups inheriting integrations for Irker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1650,6 +1918,8 @@ Count of active groups inheriting integrations for Jenkins Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1662,6 +1932,8 @@ Count of active groups inheriting integrations for Jira Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1674,6 +1946,8 @@ Count of active groups inheriting integrations for Mattermost Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1686,6 +1960,8 @@ Count of active groups inheriting integrations for Mattermost (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1698,6 +1974,8 @@ Count of active groups inheriting integrations for Microsoft Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1710,6 +1988,8 @@ Count of active groups inheriting integrations for Mock CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -1722,6 +2002,8 @@ Count of active groups inheriting integrations for Mock Monitoring Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -1734,6 +2016,8 @@ Count of active groups inheriting integrations for Packagist Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1746,6 +2030,8 @@ Count of active groups inheriting integrations for Pipeline Emails Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1758,6 +2044,8 @@ Count of active groups inheriting integrations for Pivotal Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1770,6 +2058,8 @@ Count of active groups inheriting integrations for Prometheus Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1782,6 +2072,8 @@ Count of active groups inheriting integrations for Pushover Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1794,6 +2086,8 @@ Count of active groups inheriting integrations for Redmine Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1806,6 +2100,8 @@ Count of active groups inheriting integrations for Slack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1818,6 +2114,8 @@ Count of active groups inheriting integrations for Slack (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1830,6 +2128,8 @@ Count of active groups inheriting integrations for Teamcity CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1842,6 +2142,8 @@ Count of active groups inheriting integrations for Unifiy Circuit Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1854,6 +2156,8 @@ Count of active groups inheriting integrations for Webex Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1866,6 +2170,8 @@ Count of active groups inheriting integrations for YouTrack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1878,6 +2184,8 @@ Count of groups with active integrations for Irker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1890,6 +2198,8 @@ Count of groups with active integrations for Jenkins Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1902,6 +2212,8 @@ Count of groups with active integrations for Jira Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1914,6 +2226,8 @@ Count of groups with active integrations for Mattermost Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1926,6 +2240,8 @@ Count of groups with active integrations for Mattermost (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1938,6 +2254,8 @@ Count of groups with active integrations for Microsoft Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1950,6 +2268,8 @@ Count of groups with active integrations for Mock CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -1962,6 +2282,8 @@ Count of groups with active integrations for Mock Monitoring Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -1974,6 +2296,8 @@ Count of groups with active integrations for Packagist Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1986,6 +2310,8 @@ Count of groups with active integrations for Pipeline Emails Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -1998,6 +2324,8 @@ Count of groups with active integrations for Pivotal Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2010,6 +2338,8 @@ Count of groups with active integrations for Prometheus Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2022,6 +2352,8 @@ Count of groups with active integrations for Pushover Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2034,6 +2366,8 @@ Count of groups with active integrations for Redmine Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2046,6 +2380,8 @@ Count of groups with active integrations for Slack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2058,6 +2394,8 @@ Count of groups with active integrations for Slack (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2070,6 +2408,8 @@ Count of groups with active integrations for Teamcity CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2082,6 +2422,8 @@ Count of groups with active integrations for Unifiy Circuit Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2094,6 +2436,8 @@ Count of groups with active integrations for Webex Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2106,6 +2450,8 @@ Count of groups with active integrations for YouTrack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2118,6 +2464,8 @@ Total clicks on the create track's first email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2130,6 +2478,8 @@ Total sent emails of the create track's first email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2142,6 +2492,8 @@ Total clicks on the create track's second email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2154,6 +2506,8 @@ Total sent emails of the create track's second email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2166,6 +2520,8 @@ Total clicks on the create track's third email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2178,6 +2534,8 @@ Total sent emails of the create track's third email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2190,6 +2548,8 @@ Total sent emails of the experience track's first email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2202,6 +2562,8 @@ Total clicks on the team track's first email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2214,6 +2576,8 @@ Total sent emails of the team track's first email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2226,6 +2590,8 @@ Total clicks on the team track's second email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2238,6 +2604,8 @@ Total sent emails of the team track's second email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2250,6 +2618,8 @@ Total clicks on the team track's third email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2262,6 +2632,8 @@ Total sent emails of the team track's third email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2274,6 +2646,8 @@ Total clicks on the verify trial's first email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2286,6 +2660,8 @@ Total sent emails of the trial track's first email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2298,6 +2674,8 @@ Total clicks on the trial track's second email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2310,6 +2688,8 @@ Total sent emails of the trial track's second email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2322,6 +2702,8 @@ Total clicks on the trial track's third email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2334,6 +2716,8 @@ Total sent emails of the trial track's third email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2346,6 +2730,8 @@ Total clicks on the verify track's first email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2358,6 +2744,8 @@ Total sent emails of the verify track's first email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2370,6 +2758,8 @@ Total clicks on the verify track's second email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2382,6 +2772,8 @@ Total sent emails of the verify track's second email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2394,6 +2786,8 @@ Total clicks on the verify track's third email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2406,6 +2800,8 @@ Total sent emails of the verify track's third email Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2418,6 +2814,8 @@ Missing description Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -2428,7 +2826,9 @@ Count of incidents (issues where issue_type=incident) [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180447_incident_issues.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` @@ -2440,7 +2840,9 @@ Count of all issues with the label=incident [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180451_incident_labeled_issues.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` @@ -2454,6 +2856,8 @@ Whether or not ModSecurity is set to blocking mode Group: `group::container security` +Data Category: `Operational` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -2466,6 +2870,8 @@ Whether or not ModSecurity is disabled within Ingress Group: `group::container security` +Data Category: `Operational` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -2478,6 +2884,8 @@ Whether or not ModSecurity is set to logging mode Group: `group::container security` +Data Category: `Operational` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -2490,6 +2898,8 @@ Whether or not ModSecurity has not been installed into the cluster Group: `group::container security` +Data Category: `Operational` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -2502,6 +2912,8 @@ Cumulative count of packets identified as anomalous by ModSecurity since Usage P Group: `group::container security` +Data Category: `Operational` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -2514,6 +2926,8 @@ Cumulative count of packets processed by ModSecurity since Usage Ping was last r Group: `group::container security` +Data Category: `Operational` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -2526,6 +2940,8 @@ Whether or not ModSecurity statistics are unavailable Group: `group::container security` +Data Category: `Operational` + Status: `removed` Tiers: `ultimate` @@ -2538,6 +2954,8 @@ Total GitLab Managed disabled clusters previously attached to the instance Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2550,6 +2968,8 @@ Total GitLab Managed clusters attached to the instance Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2562,6 +2982,8 @@ Count of active instance-level integrations for Asana Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2574,6 +2996,8 @@ Count of active instance-level integrations for Assembla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2586,6 +3010,8 @@ Count of active instance-level integrations for Bamboo CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2598,6 +3024,8 @@ Count of active instance-level integrations for Bugzilla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2610,6 +3038,8 @@ Count of active instance-level integrations for Buildkite Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2622,6 +3052,8 @@ Count of active instance-level integrations for Campfire Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2634,6 +3066,8 @@ Count of active instance-level integrations for Confluence Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2646,6 +3080,8 @@ Count of active instance-level integrations for a Custom Issue Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2658,6 +3094,8 @@ Count of active instance-level integrations for Datadog Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2670,6 +3108,8 @@ Count of active instance-level integrations for Discord Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2682,6 +3122,8 @@ Count of active instance-level integrations for Drone CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2694,6 +3136,8 @@ Count of active instance-level integrations for Emails on Push Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2706,6 +3150,8 @@ Count of active instance-level integrations for EWM Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2718,6 +3164,8 @@ Count of active instance-level integrations for External Wiki Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2730,6 +3178,8 @@ Count of active instance-level integrations for Flowdock Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2742,6 +3192,8 @@ Count of active instance-level integrations for GitHub Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -2754,6 +3206,8 @@ Count of active instance-level integrations for Hangouts Chat Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2766,6 +3220,8 @@ Count of active instance-level integrations for HipChat Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -2778,6 +3234,8 @@ Count of active instance-level integrations for Irker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2790,6 +3248,8 @@ Count of active instance-level integrations for Jenkins Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2802,6 +3262,8 @@ Count of active instance-level integrations for Jira Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2814,6 +3276,8 @@ Count of active instance-level integrations for Mattermost Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2826,6 +3290,8 @@ Count of active instance-level integrations for Mattermost (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2838,6 +3304,8 @@ Count of active instance-level integrations for Microsoft Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2850,6 +3318,8 @@ Count of active instance-level integrations for Mock CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -2862,6 +3332,8 @@ Count of active instance-level integrations for Mock Monitoring Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -2874,6 +3346,8 @@ Count of active instance-level integrations for Packagist Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2886,6 +3360,8 @@ Count of active instance-level integrations for Pipeline Emails Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2898,6 +3374,8 @@ Count of active instance-level integrations for Pivotal Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2910,6 +3388,8 @@ Count of active instance-level integrations for Prometheus Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2922,6 +3402,8 @@ Count of active instance-level integrations for Pushover Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2934,6 +3416,8 @@ Count of active instance-level integrations for Redmine Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2946,6 +3430,8 @@ Count of active instance-level integrations for Slack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2958,6 +3444,8 @@ Count of active instance-level integrations for Slack (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2970,6 +3458,8 @@ Count of active instance-level integrations for Teamcity CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2982,6 +3472,8 @@ Count of active instance-level integrations for Unifiy Circuit Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -2994,6 +3486,8 @@ Count of active instance-level integrations for Webex Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3006,6 +3500,8 @@ Count of active instance-level integrations for YouTrack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3018,6 +3514,8 @@ Count of Issues created Group: `group::plan` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3028,7 +3526,9 @@ Count of issues created automatically on alerts from GitLab-Managed Prometheus [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180441_issues_created_from_alerts.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` @@ -3040,11 +3540,13 @@ Count of issues manually created from the GitLab UI on Sentry errors [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180434_issues_created_from_gitlab_error_tracking_ui.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `counts.issues_created_gitlab_alerts` @@ -3052,7 +3554,9 @@ Count of all issues created from GitLab alerts (bot and non-bot) [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180443_issues_created_gitlab_alerts.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` @@ -3064,7 +3568,9 @@ Count of issues created manually by non-bot users from GitLab alerts [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180445_issues_created_manually_from_alerts.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` @@ -3076,7 +3582,9 @@ Count of issues where a user have added AND removed a zoom meeting using slash c [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180438_issues_using_zoom_quick_actions.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` @@ -3088,7 +3596,9 @@ Count of issues where a user has linked a Zoom meeting [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180436_issues_with_associated_zoom_link.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` @@ -3100,7 +3610,9 @@ Count of issues where a user has embedded a Grafana chart [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180440_issues_with_embedded_grafana_charts_approx.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` @@ -3114,6 +3626,8 @@ Count of issues with health status Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -3126,6 +3640,8 @@ Count of Projects that imported Issues from Jira Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3138,6 +3654,8 @@ Count of Jira imports completed Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3150,6 +3668,8 @@ Count of total issues imported via the Jira Importer Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3162,6 +3682,8 @@ Number of keys. Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3174,6 +3696,8 @@ Count of events when an Agent is asked to synchronize the manifests or its confi Group: `group::configure` +Data Category: `Operational` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -3186,6 +3710,8 @@ Count of Kubernetes API proxy requests Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -3198,6 +3724,8 @@ Count of Kubernetes registered agents Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -3210,6 +3738,8 @@ Count of Kubernetes agents with at least one token Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -3222,6 +3752,8 @@ Count of label lists created on Boards Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3234,6 +3766,8 @@ Count of Labels Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3246,6 +3780,8 @@ Number of groups that are synced via LDAP group sync `https://docs.gitlab.com/ee Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -3258,6 +3794,8 @@ Number of keys synced as part of LDAP `https://docs.gitlab.com/ee/administration Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -3270,6 +3808,8 @@ Number of users that are linked to LDAP Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -3282,6 +3822,8 @@ Missing description Group: `group::create` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -3294,6 +3836,8 @@ Count of License Scanning jobs run Group: `group::composition analysis` +Data Category: `Subscription` + Status: `data_available` Tiers: `ultimate` @@ -3306,6 +3850,8 @@ Count to License List page views Group: `group::composition analysis` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -3318,6 +3864,8 @@ Count of the number of merge request comments Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3330,6 +3878,8 @@ Count of the number of merge requests created Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3342,6 +3892,8 @@ Count of the number of merge requests Group: `group::code review` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3354,6 +3906,8 @@ Count of merge requests merged using approval rules Group: `group::compliance` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -3366,6 +3920,8 @@ Count of milestone lists created on Boards Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -3378,6 +3934,8 @@ Count of milestones created Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3390,6 +3948,8 @@ Total Searches using the navbar for All Basic Search and Advanced Search in self Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3402,6 +3962,8 @@ Cumulative count of packets dropped by Cilium (Container Network Security) since Group: `group::container security` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3414,6 +3976,8 @@ Cumulative count of packets forwarded by Cilium (Container Network Security) sin Group: `group::container security` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3426,6 +3990,8 @@ Count of Notes across all objects that use them Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3438,6 +4004,8 @@ Active users with enabled operations dashboard Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3450,6 +4018,8 @@ Active users with projects on operations dashboard Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3462,6 +4032,8 @@ A count of Composer packages that have been deleted Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3474,6 +4046,8 @@ A count of Composer packages that have been downloaded Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3486,6 +4060,8 @@ A count of Composer packages that have been published Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3498,6 +4074,8 @@ A count of Conan packages that have been deleted Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3510,6 +4088,8 @@ A count of Conan packages that have been downloaded Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3522,6 +4102,8 @@ A count of Conan packages that have been published Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3534,6 +4116,8 @@ A count of container images that have been deleted Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -3546,6 +4130,8 @@ A count of container images that have been downloaded Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -3558,6 +4144,8 @@ A count of container images that have been published Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -3570,6 +4158,8 @@ A count of Debian packages that have been deleted Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3582,6 +4172,8 @@ A count of Debian packages that have been downloaded Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3594,6 +4186,8 @@ A count of Debian packages that have been published Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -3606,6 +4200,8 @@ A count of packages that have been deleted Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3618,6 +4214,8 @@ A count of packages that have been deleted using a Deploy Token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3630,6 +4228,8 @@ A count of packages that have been deleted using a Guest Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3642,6 +4242,8 @@ A count of packages that have been deleted using a logged in user Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3654,6 +4256,8 @@ A count of generic packages that have been deleted Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3666,6 +4270,8 @@ A count of generic packages that have been downloaded Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3678,6 +4284,8 @@ A count of generic packages that have been published Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3690,6 +4298,8 @@ A count of Go modules that have been deleted Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3702,6 +4312,8 @@ A count of Go modules that have been downloaded Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3714,6 +4326,8 @@ A count of Go modules that have been published Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3726,6 +4340,22 @@ Total count of pull Helm packages events Group: `group::package` +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + +### `counts.package_events_i_package_helm_push_package` + +The total count of Helm packages that have been published. + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210625095025_package_events_i_package_helm_push_package.yml) + +Group: `group::package` + +Data Category: `Optional` + Status: `implemented` Tiers: `free`, `premium`, `ultimate` @@ -3738,6 +4368,8 @@ A count of Maven packages that have been deleted Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3750,6 +4382,8 @@ A count of Maven packages that have been downloaded Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3762,6 +4396,8 @@ A count of Maven packages that have been published Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3774,6 +4410,8 @@ A count of npm packages that have been deleted Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3786,6 +4424,8 @@ A count of npm packages that have been downloaded Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3798,6 +4438,8 @@ A count of npm packages that have been published Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3810,6 +4452,8 @@ A count of NuGet packages that have been deleted Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3822,10 +4466,26 @@ A count of NuGet packages that have been downloaded Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` +### `counts.package_events_i_package_nuget_pull_symbol_package` + +A count of NuGet symbol packages that have been downloaded from the package registry + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210709191135_package_events_i_package_nuget_pull_symbol_package.yml) + +Group: `group::package` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + ### `counts.package_events_i_package_nuget_push_package` A count of NuGet packages that have been published @@ -3834,10 +4494,26 @@ A count of NuGet packages that have been published Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` +### `counts.package_events_i_package_nuget_push_symbol_package` + +A count of NuGet symbol packages that have been uploaded to the package registry + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210709191829_package_events_i_package_nuget_push_symbol_package.yml) + +Group: `group::package` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + ### `counts.package_events_i_package_pull_package` A count of packages that have been downloaded from the package registry @@ -3846,6 +4522,8 @@ A count of packages that have been downloaded from the package registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3858,6 +4536,8 @@ A count of packages that have been downloaded from the package registry using a Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3870,6 +4550,8 @@ A count of packages that have been downloaded from the package registry by a gue Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3882,10 +4564,68 @@ A count of packages that have been downloaded from the package registry by a use Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` +### `counts.package_events_i_package_pull_symbol_package` + +A count of symbol packages that have been pulled from the package registry + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210709210941_package_events_i_package_pull_symbol_package.yml) + +Group: `group::package` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + +### `counts.package_events_i_package_pull_symbol_package_by_deploy_token` + +A count of symbol packages that have been pulled with a deploy token from the package registry + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210709211058_package_events_i_package_pull_symbol_package_by_deploy_token.yml) + +Group: `group::package` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + +### `counts.package_events_i_package_pull_symbol_package_by_guest` + +A count of symbol packages that have been pulled with by a guest from the package registry + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210709211248_package_events_i_package_pull_symbol_package_by_guest.yml) + +Group: `group::package` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + +### `counts.package_events_i_package_pull_symbol_package_by_user` + +A count of symbol packages that have been pulled with by an authenticated user from the package registry + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210709211341_package_events_i_package_pull_symbol_package_by_user.yml) + +Group: `group::package` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + ### `counts.package_events_i_package_push_package` A count of packages that have been published to the package registry @@ -3894,6 +4634,8 @@ A count of packages that have been published to the package registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3906,6 +4648,8 @@ A count of packages that have been published to the package registry using a dep Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3918,6 +4662,8 @@ A count of packages that have been published to the package registry by a Guest Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3930,10 +4676,68 @@ A count of packages that have been published to the package registry by a user Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` +### `counts.package_events_i_package_push_symbol_package` + +A count of symbol packages that have been pushed to the package registry + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210709211439_package_events_i_package_push_symbol_package.yml) + +Group: `group::package` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + +### `counts.package_events_i_package_push_symbol_package_by_deploy_token` + +A count of symbol packages that have been pushed with a deploy token to the package registry + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210709211636_package_events_i_package_push_symbol_package_by_deploy_token.yml) + +Group: `group::package` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + +### `counts.package_events_i_package_push_symbol_package_by_guest` + +A count of symbol packages that have been pushed by a guest to the package registry + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210709211731_package_events_i_package_push_symbol_package_by_guest.yml) + +Group: `group::package` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + +### `counts.package_events_i_package_push_symbol_package_by_user` + +A count of symbol packages that have been pushed by an authenticated user to the package registry + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210709211831_package_events_i_package_push_symbol_package_by_user.yml) + +Group: `group::package` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + ### `counts.package_events_i_package_pypi_delete_package` A count of Python packages that have been deleted from the package registry @@ -3942,6 +4746,8 @@ A count of Python packages that have been deleted from the package registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3954,6 +4760,8 @@ A count of Python packages that have been downloaded from the package registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3966,6 +4774,8 @@ A count of Python packages that have been published to the package registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3978,6 +4788,8 @@ Total count of RubyGems packages delete events Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -3990,6 +4802,8 @@ Total count of pull RubyGems packages events Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4002,6 +4816,8 @@ Total count of push RubyGems packages events Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4014,6 +4830,8 @@ A count of package tags that have been deleted from the package registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -4026,6 +4844,8 @@ A count of package tags that have been downloaded from the package registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -4038,6 +4858,8 @@ A count of package tags that have been published to the package registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -4050,6 +4872,8 @@ Total count of Terraform Module packages delete events Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4062,6 +4886,8 @@ Total count of pull Terraform Module packages events Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4074,6 +4900,8 @@ Total count of push Terraform Module packages events Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4086,6 +4914,8 @@ The total number of packages published to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4098,6 +4928,8 @@ Total GitLab Pages domains Group: `group::release management` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -4110,6 +4942,8 @@ Count of personal Snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4122,6 +4956,8 @@ Count the total number of log views Group: `group::monitor` +Data Category: `Optional` + Status: `removed` Tiers: `free` @@ -4134,6 +4970,8 @@ Count of unique object pool repositories for fork deduplication Group: `group::gitaly` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4146,6 +4984,8 @@ Total visits to /groups/:group/-/analytics/productivity_analytics all time Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4158,6 +4998,8 @@ Total GitLab Managed disabled clusters previously attached to projects Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4170,6 +5012,8 @@ Total GitLab Managed clusters attached to projects Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4182,6 +5026,8 @@ Count of project Snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4194,6 +5040,8 @@ Count of Projects created Group: `group::project management` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4206,6 +5054,8 @@ Count of projects with active integrations for Asana Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4218,6 +5068,8 @@ Count of projects with active integrations for Assembla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4230,6 +5082,8 @@ Count of projects with active integrations for Bamboo CI Group: `group::ecosystem` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4242,6 +5096,8 @@ Count of projects with active integrations for Bugzilla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4254,6 +5110,8 @@ Count of projects with active integrations for Buildkite Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4266,6 +5124,8 @@ Count of projects with active integrations for Campfire Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4278,6 +5138,8 @@ Count of projects with active integrations for Confluence Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4288,11 +5150,13 @@ Counts of Projects that have incident issues, regardless of status. [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180453_projects_creating_incidents.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `counts.projects_custom_issue_tracker_active` @@ -4302,6 +5166,8 @@ Count of projects with active integrations for a Custom Issue Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4314,6 +5180,8 @@ Count of projects with active integrations for Datadog Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4326,6 +5194,8 @@ Count of projects with active integrations for Discord Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4338,6 +5208,8 @@ Count of projects with active integrations for Drone CI Group: `group::ecosystem` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4350,6 +5222,8 @@ Count of projects with active integrations for Emails on Push Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4362,6 +5236,8 @@ Count of projects with active integrations for EWM Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4374,6 +5250,8 @@ Count of projects with active integrations for External Wiki Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4386,6 +5264,8 @@ Count of projects with active integrations for Flowdock Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4398,6 +5278,8 @@ Count of projects with active integrations for GitHub Group: `group::ecosystem` +Data Category: `Operational` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -4410,6 +5292,8 @@ Count of projects with active integrations for Hangouts Chat Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4422,6 +5306,8 @@ Count of projects with active integrations for HipChat Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -4434,6 +5320,8 @@ Missing description Group: `group::import` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -4446,6 +5334,8 @@ Count of active projects inheriting integrations for Asana Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4458,6 +5348,8 @@ Count of active projects inheriting integrations for Assembla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4470,6 +5362,8 @@ Count of active projects inheriting integrations for Bamboo CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4482,6 +5376,8 @@ Count of active projects inheriting integrations for Bugzilla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4494,6 +5390,8 @@ Count of active projects inheriting integrations for Buildkite Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4506,6 +5404,8 @@ Count of active projects inheriting integrations for Campfire Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4518,6 +5418,8 @@ Count of active projects inheriting integrations for Confluence Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4530,6 +5432,8 @@ Count of active projects inheriting integrations for a Custom Issue Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4542,6 +5446,8 @@ Count of active projects inheriting integrations for Datadog Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4554,6 +5460,8 @@ Count of active projects inheriting integrations for Discord Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4566,6 +5474,8 @@ Count of active projects inheriting integrations for Drone CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4578,6 +5488,8 @@ Count of active projects inheriting integrations for Emails on Push Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4590,6 +5502,8 @@ Count of active projects inheriting integrations for EWM Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4602,6 +5516,8 @@ Count of active projects inheriting integrations for External Wiki Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4614,6 +5530,8 @@ Count of active projects inheriting integrations for Flowdock Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4626,6 +5544,8 @@ Count of active projects inheriting integrations for GitHub Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -4638,6 +5558,8 @@ Count of active projects inheriting integrations for Hangouts Chat Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4650,6 +5572,8 @@ Count of active projects inheriting integrations for HipChat Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -4662,6 +5586,8 @@ Count of active projects inheriting integrations for Irker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4674,6 +5600,8 @@ Count of active projects inheriting integrations for Jenkins Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4686,6 +5614,8 @@ Count of active projects inheriting integrations for Jira Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4698,6 +5628,8 @@ Count of active projects inheriting integrations for Mattermost Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4710,6 +5642,8 @@ Count of active projects inheriting integrations for Mattermost (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4722,6 +5656,8 @@ Count of active projects inheriting integrations for Microsoft Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4734,6 +5670,8 @@ Count of active projects inheriting integrations for Mock CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -4746,6 +5684,8 @@ Count of active projects inheriting integrations for Mock Monitoring Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -4758,6 +5698,8 @@ Count of active projects inheriting integrations for Packagist Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4770,6 +5712,8 @@ Count of active projects inheriting integrations for Pipeline Emails Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4782,6 +5726,8 @@ Count of active projects inheriting integrations for Pivotal Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4794,6 +5740,8 @@ Count of active projects inheriting integrations for Prometheus Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4806,6 +5754,8 @@ Count of active projects inheriting integrations for Pushover Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4818,6 +5768,8 @@ Count of active projects inheriting integrations for Redmine Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4830,6 +5782,8 @@ Count of active projects inheriting integrations for Slack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4842,6 +5796,8 @@ Count of active projects inheriting integrations for Slack (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4854,6 +5810,8 @@ Count of active projects inheriting integrations for Teamcity CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4866,6 +5824,8 @@ Count of active projects inheriting integrations for Unifiy Circuit Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4878,6 +5838,8 @@ Count of active projects inheriting integrations for Webex Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4890,6 +5852,8 @@ Count of active projects inheriting integrations for YouTrack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4902,6 +5866,8 @@ Count of projects with active integrations for Irker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4914,6 +5880,8 @@ Count of projects with active integrations for Jenkins Group: `group::ecosystem` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4926,6 +5894,8 @@ Count of projects with active integrations for Jira Group: `group::ecosystem` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4938,6 +5908,8 @@ Count of active integrations with Jira Cloud (Saas) Group: `group::ecosystem` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4950,6 +5922,8 @@ Count of active integrations with Jira Cloud (DVCS Connector) Group: `group::ecosystem` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4962,6 +5936,8 @@ Count of active integrations with Jira Software (DVCS connector) Group: `group::ecosystem` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4974,6 +5950,8 @@ Total Jira Issue feature enabled Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -4986,6 +5964,8 @@ Count of active integrations with Jira Software (server) Group: `group::ecosystem` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -4998,6 +5978,8 @@ Count of projects with active integrations for Mattermost Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5010,6 +5992,8 @@ Count of projects with active integrations for Mattermost (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5022,6 +6006,8 @@ Count of projects with active integrations for Microsoft Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5034,6 +6020,8 @@ Projects with repository mirroring enabled Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -5046,6 +6034,8 @@ Count of projects with active integrations for Mock CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -5058,6 +6048,8 @@ Count of projects with active integrations for Mock Monitoring Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -5070,6 +6062,8 @@ Count of projects with active integrations for Packagist Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5082,6 +6076,8 @@ Count of projects with active integrations for Pipeline Emails Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5094,6 +6090,8 @@ Count of projects with active integrations for Pivotal Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5106,6 +6104,8 @@ Count of projects with active integrations for Prometheus Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5118,6 +6118,8 @@ Count of projects with active integrations for Pushover Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5130,6 +6132,8 @@ Count of projects with active integrations for Redmine Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5142,6 +6146,8 @@ Projects with a GitHub service pipeline enabled Group: `group::continuous_integration` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -5154,6 +6160,8 @@ Count of projects with active integrations for Slack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5166,6 +6174,8 @@ Count of projects with active integrations for Slack (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5178,6 +6188,8 @@ Count of projects with active integrations for Teamcity CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5190,6 +6202,8 @@ Count of projects with active integrations for Unifiy Circuit Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5202,6 +6216,8 @@ Count of projects with active integrations for Webex Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5212,11 +6228,13 @@ Count of projects with alerts created in given time period [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180458_projects_with_alerts_created.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `counts.projects_with_alerts_service_enabled` @@ -5224,7 +6242,9 @@ Count of projects that have enabled the Alerts service [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180456_projects_with_alerts_service_enabled.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `removed` @@ -5236,11 +6256,13 @@ Count of projects with at least 1 enabled integration [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180500_projects_with_enabled_alert_integrations.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `counts.projects_with_error_tracking_enabled` @@ -5248,7 +6270,9 @@ Count of projects that have enabled Error tracking via Sentry [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180454_projects_with_error_tracking_enabled.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` @@ -5262,6 +6286,8 @@ The number of projects with cleanup policy for tags turned off Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5274,6 +6300,8 @@ A count of projects with the cleanup policy for tags turned on Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5286,6 +6314,8 @@ A count of projects with the cleanup policy set to run every 14 days Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5298,6 +6328,8 @@ A count of projects with the cleanup policy set to run every day Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5310,6 +6342,8 @@ A count of projects with the cleanup policy set to run monthly Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5322,6 +6356,8 @@ A count of projects with the cleanup policy set to run every 3 months Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5334,6 +6370,8 @@ A count of projects with the cleanup policy set to run every 7 days Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5346,6 +6384,8 @@ A count of projects with the cleanup policy set to keep 1 tag Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5358,6 +6398,8 @@ A count of projects with the cleanup policy set to keep 10 tags Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5370,6 +6412,8 @@ A count of projects with the cleanup policy set to keep 100 tags Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5382,6 +6426,8 @@ A count of projects with the cleanup policy set to keep 25 tags Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5394,6 +6440,8 @@ A count of projects with the cleanup policy set to keep 5 tags Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5406,6 +6454,8 @@ A count of projects with the cleanup policy set to keep 50 tags Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5418,6 +6468,8 @@ A count of projects with the cleanup policy with the number of tags to keep unse Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5430,6 +6482,8 @@ A count of projects with the cleanup policy set delete tags older than 14 days Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5442,6 +6496,8 @@ A count of projects with the cleanup policy set delete tags older than 30 days Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5454,6 +6510,8 @@ A count of projects with the cleanup policy set delete tags older than 7 days Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5466,6 +6524,8 @@ A count of projects with the cleanup policy set delete tags older than 90 days Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5478,6 +6538,8 @@ A count of projects with the cleanup policy with the number of tags to delete un Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5490,6 +6552,8 @@ Projects with package registry enabled Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5502,6 +6566,8 @@ Projects with Prometheus alerting enabled Group: `group::monitor` +Data Category: `Optional` + Status: `removed` Tiers: `free` @@ -5514,6 +6580,8 @@ Count of users creating projects that have a matching Git repository, result of Group: `group::source code` +Data Category: `Operational` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -5526,6 +6594,8 @@ Count of projects with Terraform MR reports Group: `group::configure` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5538,6 +6608,8 @@ Count of projects with GitLab Managed Terraform State Group: `group::configure` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5550,6 +6622,8 @@ Projects with tracing enabled Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5562,6 +6636,8 @@ Count of projects with active integrations for YouTrack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5574,6 +6650,8 @@ Count of total protected branches Group: `group::source code` +Data Category: `Operational` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -5586,6 +6664,8 @@ Count of branches that have been protected and are not the default branch Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5598,6 +6678,8 @@ Unique release tags Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -5610,6 +6692,8 @@ Count of total remote mirrors. Includes both push and pull mirrors Group: `group::source code` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5622,6 +6706,8 @@ Count of requirement test reports created from CI Group: `group::certify` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -5634,6 +6720,8 @@ Count of requirement test reports created manually Group: `group::certify` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -5646,6 +6734,8 @@ Count of requirements created Group: `group::certify` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -5658,6 +6748,8 @@ Count of requirements having a test report Group: `group::certify` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -5670,18 +6762,22 @@ Count of SAST CI jobs for the month. Job names ending in '-sast' Group: `group::static analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts.secret_detection_jobs` -Count of 'secret-detection' CI jobs fro the month. +Count of all 'secret-detection' CI jobs. [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216182114_secret_detection_jobs.yml) Group: `group::static analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5694,6 +6790,8 @@ Count of service desk enabled projects Group: `group::certify` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -5706,6 +6804,8 @@ Count of service desk issues Group: `group::certify` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -5718,6 +6818,8 @@ Count of comments on Snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5730,6 +6832,8 @@ Count of newly created Snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5742,6 +6846,8 @@ Count of updates to existing Snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5754,6 +6860,8 @@ Count of all Snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5766,6 +6874,8 @@ Count of total Git push operations Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5778,6 +6888,8 @@ Count of commits created from the Static Site Editor Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5790,6 +6902,8 @@ Count of merge requests created via Static Site Editor Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5802,6 +6916,8 @@ Count of Static Site Editor views Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5810,49 +6926,57 @@ Tiers: `free`, `premium`, `ultimate` Cumulative count of usages of publish operation -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180502_status_page_incident_publishes.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216180502_status_page_incident_publishes.yml) + +Group: `group::monitor` -Group: `group::health` +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `ultimate` ### `counts.status_page_incident_unpublishes` Cumulative count of usages of unpublish operation -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180504_status_page_incident_unpublishes.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216180504_status_page_incident_unpublishes.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `ultimate` ### `counts.status_page_issues` Issues published to a Status Page -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180507_status_page_issues.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216180507_status_page_issues.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `ultimate` ### `counts.status_page_projects` Projects with status page enabled -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180506_status_page_projects.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216180506_status_page_projects.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `ultimate` ### `counts.successful_deployments` @@ -5862,6 +6986,8 @@ Total successful deployments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -5874,6 +7000,8 @@ Count of all comments that contain suggested changes Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5886,6 +7014,8 @@ Count of total repo templates used to aggregate all file templates Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -5898,6 +7028,8 @@ Count of active service templates for Asana Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5910,6 +7042,8 @@ Count of active service templates for Assembla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5922,6 +7056,8 @@ Count of active service templates for Bamboo CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5934,6 +7070,8 @@ Count of active service templates for Bugzilla Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5946,6 +7084,8 @@ Count of active service templates for Buildkite Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5958,6 +7098,8 @@ Count of active service templates for Campfire Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5970,6 +7112,8 @@ Count of active service templates for Confluence Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5982,6 +7126,8 @@ Count of active service templates for a Custom Issue Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -5994,6 +7140,8 @@ Count of active service templates for Datadog Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6006,6 +7154,8 @@ Count of active service templates for Discord Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6018,6 +7168,8 @@ Count of active service templates for Drone CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6030,6 +7182,8 @@ Count of active service templates for Emails on Push Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6042,6 +7196,8 @@ Count of active service templates for EWM Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6054,6 +7210,8 @@ Count of active service templates for External Wiki Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6066,6 +7224,8 @@ Count of active service templates for Flowdock Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6078,6 +7238,8 @@ Count of active service templates for GitHub Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -6090,6 +7252,8 @@ Count of active service templates for Hangouts Chat Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6102,6 +7266,8 @@ Count of active service templates for HipChat Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -6114,6 +7280,8 @@ Count of active service templates for Irker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6126,6 +7294,8 @@ Count of active service templates for Jenkins Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6138,6 +7308,8 @@ Count of active service templates for Jira Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6150,6 +7322,8 @@ Count of active service templates for Mattermost Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6162,6 +7336,8 @@ Count of active service templates for Mattermost (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6174,6 +7350,8 @@ Count of active service templates for Microsoft Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6186,6 +7364,8 @@ Count of active service templates for Mock CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -6198,6 +7378,8 @@ Count of active service templates for Mock Monitoring Group: `group::ecosystem` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -6210,6 +7392,8 @@ Count of active service templates for Packagist Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6222,6 +7406,8 @@ Count of active service templates for Pipeline Emails Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6234,6 +7420,8 @@ Count of active service templates for Pivotal Tracker Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6246,6 +7434,8 @@ Count of active service templates for Prometheus Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6258,6 +7448,8 @@ Count of active service templates for Pushover Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6270,6 +7462,8 @@ Count of active service templates for Redmine Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6282,6 +7476,8 @@ Count of active service templates for Slack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6294,6 +7490,8 @@ Count of active service templates for Slack (slash commands) Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6306,6 +7504,8 @@ Count of active service templates for Teamcity CI Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6318,6 +7518,8 @@ Count of active service templates for Unifiy Circuit Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6330,6 +7532,8 @@ Count of active service templates for Webex Teams Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6342,6 +7546,8 @@ Count of active service templates for YouTrack Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6354,6 +7560,8 @@ Count of Terraform MR reports generated Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6366,6 +7574,8 @@ Count of GitLab Managed Terraform States Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6378,6 +7588,8 @@ Count of todos created Group: `group::project management` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6390,6 +7602,8 @@ Count of Uploads via Notes and Descriptions Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6402,6 +7616,8 @@ Count of users who set personal preference to see Details on Group information p Group: `group::threat insights` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -6414,6 +7630,8 @@ Count of users who set personal preference to see Security Dashboard on Group in Group: `group::threat insights` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -6426,6 +7644,8 @@ Count of users with the GitPod integration enabled Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6438,6 +7658,8 @@ Missing description Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -6450,6 +7672,8 @@ Count of commits made from the Web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6462,6 +7686,8 @@ Count of merge requests created from the Web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6474,6 +7700,8 @@ Count of Pipeline tab views in the Web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6486,6 +7714,8 @@ Count of Live Preview tab views in the Web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6498,6 +7728,8 @@ Count of Web Terminal tab views in the Web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6510,6 +7742,8 @@ Count of views of the Web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6522,6 +7756,8 @@ Count of all Wiki pages created Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6534,6 +7770,8 @@ Count of all Wiki pages deleted Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6546,6 +7784,8 @@ Count of all Wiki page updates Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6558,6 +7798,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -6570,6 +7812,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6582,6 +7826,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6594,21 +7840,25 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts_monthly.aggregated_metrics.compliance_features_track_unique_visits_union` -Missing description +Unique users that have used audit event screen, audit event API, compliance dashboard, or credential inventory -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183201_compliance_features_track_unique_visits_union.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210216183201_compliance_features_track_unique_visits_union.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `counts_monthly.aggregated_metrics.i_testing_paid_monthly_active_user_total` @@ -6618,6 +7868,8 @@ Aggregated count of users who have engaged with a Premium or Ultimate tier testi Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -6628,11 +7880,13 @@ Count of unique users per month to take an action on an alert [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180509_incident_management_alerts_total_unique_counts.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `counts_monthly.aggregated_metrics.incident_management_incidents_total_unique_counts` @@ -6640,11 +7894,13 @@ Count of unique users per month to take an action on an incident [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180511_incident_management_incidents_total_unique_counts.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `counts_monthly.aggregated_metrics.product_analytics_test_metrics_intersection` @@ -6654,6 +7910,8 @@ This was test metric used for purpose of assuring correct implementation of aggr Group: `group::product intelligence` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -6666,6 +7924,8 @@ This was test metric used for purpose of assuring correct implementation of aggr Group: `group::product intelligence` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -6678,6 +7938,8 @@ Total deployments count for recent 28 days Group: `group::ops release` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6690,6 +7952,8 @@ Total failed deployments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -6702,6 +7966,8 @@ A monthly count of packages published to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6714,6 +7980,8 @@ Monthly count of personal Snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6726,6 +7994,8 @@ Monthly count of project Snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6738,6 +8008,8 @@ Count number of projects created monthly Group: `group::project management` +Data Category: `Optional` + Status: `implemented` Tiers: `free`, `premium`, `ultimate` @@ -6750,6 +8022,8 @@ Monthly count of unique projects with HTTP alerting enabled Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6762,6 +8036,8 @@ Monthly count of All Snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6774,6 +8050,8 @@ Total successful deployments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -6786,6 +8064,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6798,6 +8078,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6810,21 +8092,25 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `counts_weekly.aggregated_metrics.compliance_features_track_unique_visits_union` -Missing description +Unique users that have used audit event screen, audit event API, compliance dashboard, or credential inventory [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216183211_compliance_features_track_unique_visits_union.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `premium`, `ultimate` ### `counts_weekly.aggregated_metrics.i_testing_paid_monthly_active_user_total` @@ -6834,6 +8120,8 @@ Aggregated count of users who have engaged with a Premium or Ultimate tier testi Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -6842,25 +8130,29 @@ Tiers: `premium`, `ultimate` Count of unique users per week to take an action on an alert -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180513_incident_management_alerts_total_unique_counts.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180513_incident_management_alerts_total_unique_counts.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `counts_weekly.aggregated_metrics.incident_management_incidents_total_unique_counts` Count of unique users per week to take an action on an incident -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180515_incident_management_incidents_total_unique_counts.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180515_incident_management_incidents_total_unique_counts.yml) + +Group: `group::monitor` -Group: `group::health` +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `counts_weekly.aggregated_metrics.product_analytics_test_metrics_intersection` @@ -6870,6 +8162,8 @@ This was test metric used for purpose of assuring correct implementation of aggr Group: `group::product intelligence` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -6882,6 +8176,8 @@ This was test metric used for purpose of assuring correct implementation of aggr Group: `group::product intelligence` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -6894,6 +8190,8 @@ This metric only returns a value of PostgreSQL in supported versions of GitLab. Group: `group::enablement distribution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6906,6 +8204,8 @@ TBD Group: `group::distribution` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -6918,6 +8218,8 @@ The version of the PostgreSQL database. Group: `group::distribution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6930,6 +8232,8 @@ A count of projects where the dependency proxy is enabled Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6942,6 +8246,8 @@ Edition of GitLab such as EE or CE Group: `group::distribution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6954,6 +8260,8 @@ Whether Elasticsearch is enabled Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -6966,6 +8274,8 @@ Is Geo enabled? Group: `group::geo` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -6978,6 +8288,8 @@ Information about Git version Group: `group::distribution` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -6990,6 +8302,8 @@ Total GitLab Managed clusters both enabled and disabled Group: `group::product intelligence` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -7002,6 +8316,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7014,6 +8330,8 @@ Total Gitalty Servers Group: `group::product intelligence` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -7026,6 +8344,8 @@ Version of Gitaly Group: `group::product intelligence` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -7038,6 +8358,8 @@ Whether GitLab Pages is enabled Group: `group::product intelligence` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7050,6 +8372,8 @@ The version number of GitLab Pages Group: `group::product intelligence` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7062,6 +8386,8 @@ Whether shared runners is enabled Group: `group::runner` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7074,6 +8400,8 @@ Whether Gitpod is enabled in the instance Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7086,6 +8414,8 @@ Whether Grafana is enabled Group: `group::product intelligence` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7098,6 +8428,8 @@ Whether gravatar is enabled Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7110,6 +8442,8 @@ The peak active user count. Active is defined in UsersStatistics model. Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7122,6 +8456,8 @@ Host name of GitLab instance Group: `group::product intelligence` +Data Category: `Standard` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7134,6 +8470,8 @@ Whether or not ModSecurity is enabled within Ingress Group: `group::container security` +Data Category: `Operational` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -7146,6 +8484,8 @@ The installation method used to install GitLab (Omnibus, Helm, etc) Group: `group::distribution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7158,6 +8498,8 @@ Whether auto DevOps is enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7170,6 +8512,8 @@ Whether LDAP is enabled Group: `group::product intelligence` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7182,6 +8526,8 @@ Number of all billable users (active users excluding bots and guests). Group: `group::product intelligence` +Data Category: `Optional` + Status: `implemented` Tiers: `premium`, `ultimate` @@ -7194,6 +8540,8 @@ The date the license ends Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7206,6 +8554,8 @@ The ID of the license Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7218,6 +8568,8 @@ The MD5 hash of license key of the GitLab instance Group: `group::license` +Data Category: `Standard` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7230,6 +8582,8 @@ The plan of the GitLab license Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7242,6 +8596,8 @@ The date the license starts Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7254,6 +8610,8 @@ Licese zuora_subscription_id Group: `group::license` +Data Category: `Standard` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7266,6 +8624,8 @@ Whether this is a trial license or not Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7278,6 +8638,8 @@ Date the trial license ends on Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7290,6 +8652,8 @@ The number of seats included in the license Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7302,6 +8666,8 @@ Company on the GitLab license Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7314,6 +8680,8 @@ Email on the GitLab license Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7326,6 +8694,8 @@ Name on the GitLab license Group: `group::license` +Data Category: `Subscription` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7338,6 +8708,8 @@ The value of the SMTP server that is used Group: `group::activation` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7350,6 +8722,8 @@ Whether Mattermost is enabled Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7362,6 +8736,8 @@ Whether Object Storage is enabled for Artifacts Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7374,6 +8750,8 @@ Whether Background Upload for Object Storage is enabled for Artifacts Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7386,6 +8764,8 @@ Whether Direct Upload for Object Storage is enabled for Artifacts Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7398,6 +8778,8 @@ Whether Object Storage is enabled for Artifacts Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7410,6 +8792,8 @@ What Object Storage provider has been configured for Artifacts Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7422,6 +8806,8 @@ Whether Object Storage is enabled for External Diffs Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7434,6 +8820,8 @@ Whether Background Upload for Object Storage is enabled for External Diffs Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7446,6 +8834,8 @@ Whether Direct Upload for Object Storage is enabled for External Diffs Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7458,6 +8848,8 @@ Whether Object Storage is enabled for External Diffs Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7470,6 +8862,8 @@ What Object Storage provider has been configured for External Diffs Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7482,6 +8876,8 @@ Whether Object Storage is enabled for LFS Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7494,6 +8890,8 @@ Whether Background Upload for Object Storage is enabled for LFS Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7506,6 +8904,8 @@ Whether Direct Upload for Object Storage is enabled for LFS Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7518,6 +8918,8 @@ Whether Object Storage is enabled for LFS Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7530,6 +8932,8 @@ What Object Storage provider has been configured for LFS Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7542,6 +8946,8 @@ Whether Object Storage is enabled for Uploads Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7554,6 +8960,8 @@ Whether Background Upload for Object Storage is enabled for Packages Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7566,6 +8974,8 @@ Whether Direct Upload for Object Storage is enabled for Packages Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7578,6 +8988,8 @@ Whether Object Storage is enabled for Packages Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7590,6 +9002,8 @@ What Object Storage provider has been configured for Packages Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7602,6 +9016,8 @@ Whether Object Storage is enabled for Uploads Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7614,6 +9030,8 @@ Whether Background Upload for Object Storage is enabled for Uploads Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7626,6 +9044,8 @@ Whether Direct Upload for Object Storage is enabled for Uploads Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7638,6 +9058,8 @@ Whether Object Storage is enabled for Uploads Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7650,6 +9072,8 @@ What Object Storage provider has been configured for Uploads Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7662,6 +9086,8 @@ Whether OmniAuth is enabled Group: `group::product intelligence` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7674,6 +9100,8 @@ Whether the bundled Prometheus is enabled Group: `group::product intelligence` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7686,6 +9114,8 @@ Whether Prometheus Metrics endpoint is enabled Group: `group::product intelligence` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7698,6 +9128,8 @@ When the Usage Ping computation was started Group: `group::product intelligence` +Data Category: `Standard` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7710,6 +9142,8 @@ When the core features were computed Group: `group::product intelligence` +Data Category: `Standard` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -7722,6 +9156,8 @@ When the EE-specific features were computed Group: `group::product intelligence` +Data Category: `Standard` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7734,6 +9170,8 @@ The number of unique users who visited any analytics feature by month Group: `group::optimize` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -7746,6 +9184,8 @@ The number of unique users who visited any analytics feature by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -7758,6 +9198,8 @@ Unique visitors to /groups/:group/-/contribution_analytics by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7770,6 +9212,8 @@ Unique visitors to /groups/:group/-/contribution_analytics by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -7782,6 +9226,8 @@ Unique visitors to /groups/:group/-/insights/ by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7794,6 +9240,8 @@ Unique visitors to /groups/:group/-/insights/ by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -7806,6 +9254,8 @@ Unique visitors to /groups/:group/-/issues_analytics by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7818,6 +9268,8 @@ Unique visitors to /groups/:group/-/issues_analytics by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -7830,6 +9282,8 @@ Missing description Group: `group::optimize` +Data Category: `Optional` + Status: `removed` Tiers: `free` @@ -7842,6 +9296,8 @@ Missing description Group: `group::optimize` +Data Category: `Optional` + Status: `removed` Tiers: @@ -7854,6 +9310,8 @@ Unique visitors to /groups/:group/-/analytics/productivity_analytics by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7866,6 +9324,8 @@ Unique visitors to /groups/:group/-/analytics/productivity_analytics by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -7878,6 +9338,8 @@ Unique visitors to /groups/:group/-/analytics/value_stream_analytics by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7890,6 +9352,8 @@ Unique visitors to /groups/:group/-/analytics/value_stream_analytics by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -7902,6 +9366,8 @@ Missing description Group: `group::utilization` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7914,6 +9380,8 @@ Missing description Group: `group::utilization` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -7926,6 +9394,8 @@ Counts visits to DevOps Adoption page per month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7938,6 +9408,8 @@ Counts visits to DevOps Adoption page per week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -7950,6 +9422,8 @@ Unique visitors to /admin/dev_ops_report by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7962,6 +9436,8 @@ Unique visitors to /admin/dev_ops_report by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -7974,6 +9450,8 @@ Unique visitors to /admin/usage_trends by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -7986,6 +9464,8 @@ Unique visitors to /admin/usage_trends by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -7998,6 +9478,8 @@ Unique visitors to /:group/:project/-/analytics/code_reviews by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8010,6 +9492,8 @@ Unique visitors to /:group/:project/-/analytics/code_reviews by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8022,6 +9506,8 @@ Unique visitors to /:group/:project/insights/ by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8034,6 +9520,8 @@ Unique visitors to /:group/:project/insights/ by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8046,6 +9534,8 @@ Unique visitors to /:group/:project/-/analytics/issues_analytics by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8058,6 +9548,8 @@ Unique visitors to /:group/:project/-/analytics/issues_analytics by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8070,6 +9562,8 @@ Unique visitors to /:group/:project/-/analytics/merge_request_analytics by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8082,6 +9576,8 @@ Unique visitors to /:group/:project/-/analytics/merge_request_analytics by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8094,6 +9590,8 @@ Unique visitors to /groups/:group/-/analytics/ci_cd by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8106,6 +9604,8 @@ Unique visitors to /groups/:group/-/analytics/ci_cd by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8118,6 +9618,8 @@ Unique visitors to /:group/:project/-/graphs/master/charts by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8130,6 +9632,8 @@ Unique visitors to /:group/:project/-/graphs/master/charts by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8142,6 +9646,8 @@ Unique visitors to /:group/:project/-/value_stream_analytics by month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8154,6 +9660,8 @@ Unique visitors to /:group/:project/-/value_stream_analytics by week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8166,6 +9674,8 @@ Counts visits to DevOps Adoption page per month Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -8178,6 +9688,8 @@ Counts visits to DevOps Adoption page per week Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -8190,6 +9702,8 @@ Monthly active users creating pipelines that that have the Vault JWT with it.' Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -8202,6 +9716,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8214,6 +9730,8 @@ Total count of pipelines runs Group: `group::configure` +Data Category: `Optional` + Status: `broken` Tiers: `free`, `premium`, `ultimate` @@ -8226,6 +9744,8 @@ Total count of pipelines runs Group: `group::configure` +Data Category: `Optional` + Status: `broken` Tiers: `free`, `premium`, `ultimate` @@ -8238,6 +9758,8 @@ Number of projects using 5 min production app CI template in last 7 days. Group: `group::5-min-app` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8250,6 +9772,8 @@ Number of projects using 5 min production app CI template in last 7 days. Group: `group::5-min-app` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8262,6 +9786,8 @@ Count of pipelines using the Auto Build template Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8274,6 +9800,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8286,6 +9814,8 @@ Count of pipelines using the latest Auto Deploy template Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8298,6 +9828,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8310,6 +9842,8 @@ Count of pipelines using the stable Auto Deploy template Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8322,6 +9856,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8334,6 +9870,8 @@ Count of pipelines using the Auto DevOps template Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8346,6 +9884,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8358,6 +9898,8 @@ Count of projects using `AWS/CF-Provision-and-Deploy-EC2.gitlab-ci.yml` template Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8370,6 +9912,8 @@ Count of projects using `AWS/CF-Provision-and-Deploy-EC2.gitlab-ci.yml` template Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8382,6 +9926,8 @@ Count of projects using `AWS/Deploy-ECS.gitlab-ci.yml` template in last 28 days. Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8394,6 +9940,8 @@ Count of projects using `AWS/Deploy-ECS.gitlab-ci.yml` template in last 7 days. Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8406,6 +9954,8 @@ Count of pipelines with implicit Auto Build runs Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8418,6 +9968,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8430,6 +9982,8 @@ Count of pipelines with implicit Auto Deploy runs Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8442,6 +9996,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8454,6 +10010,8 @@ Count of pipelines with implicit Auto DevOps runs Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8466,6 +10024,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8478,6 +10038,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8490,6 +10052,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8502,6 +10066,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8514,6 +10080,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8526,6 +10094,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8538,6 +10108,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8550,6 +10122,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -8562,6 +10136,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8574,6 +10150,8 @@ Count of pipelines that include the terraform base template from GitLab Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8586,6 +10164,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -8598,6 +10178,8 @@ Count of unique users per month who interact with a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8610,6 +10192,8 @@ Count of unique users per week who interact with a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8622,6 +10206,8 @@ Count of users clicking diff view setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8634,6 +10220,8 @@ Count of users clicking diff view setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8646,6 +10234,8 @@ Count of users clicking merge request file browser setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8658,6 +10248,8 @@ Count of users with merge request file list setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8670,6 +10262,8 @@ Count of users clicking single file mode setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8682,6 +10276,8 @@ Count of users clicking single file mode setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8694,6 +10290,8 @@ Count of users clicking merge request whitespae setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8706,6 +10304,8 @@ Count of users clicking merge request whitespae setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8718,6 +10318,8 @@ Count of users with show whitespace disabled Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8730,6 +10332,8 @@ Count of users with show whitespace disabled Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8742,6 +10346,8 @@ Count of users with single mode disabled Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8754,6 +10360,8 @@ Count of users with single mode disabled Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8766,6 +10374,8 @@ Count of users with show whitespace enabled Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8778,6 +10388,8 @@ Count of users with show whitespace enabled Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8790,6 +10402,8 @@ Count of users with single file mode enabled Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8802,6 +10416,8 @@ Count of users with single file mode enabled Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8814,6 +10430,8 @@ Count of users with merge request view type as inline Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8826,6 +10444,8 @@ Count of users with merge request view type as inline Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8838,6 +10458,8 @@ Count of users with merge request view type as parallel Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8850,6 +10472,8 @@ Count of users with merge request view type as parallel Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8862,6 +10486,8 @@ Count of unique users per month who edit the description of a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8874,6 +10500,8 @@ Count of unique users per week who edit the description of a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8886,6 +10514,8 @@ Count of unique users per month who edit the title of a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8898,6 +10528,8 @@ Count of unique users per week who edit the title of a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8910,6 +10542,8 @@ Count of users with merge request file list setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8922,6 +10556,8 @@ Count of users with merge request file list setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8934,6 +10570,8 @@ Count of users with merge request file tree setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8946,6 +10584,8 @@ Count of users with merge request file tree setting Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8958,6 +10598,8 @@ Count of unique merge requests per month with diffs viewed Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8970,6 +10612,8 @@ Count of unique merge requests per week with diffs viewed Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8982,6 +10626,8 @@ Count of unique merge requests per month with diffs viewed file by file Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -8994,6 +10640,8 @@ Count of unique merge requests per week with diffs viewed file by file Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9006,6 +10654,8 @@ Count of unique users per month who added a suggestion Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9018,6 +10668,8 @@ Count of unique users per week who added a suggestion Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9030,6 +10682,8 @@ Count of unique users per month who applied a suggestion Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9042,6 +10696,8 @@ Count of unique users per week who applied a suggestion Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9054,6 +10710,8 @@ Count of unique users per month who add an approval rule to a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9066,6 +10724,8 @@ Count of unique users per week who add an approval rule to a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9078,6 +10738,8 @@ Count of unique users per month who delete an approval rule to a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9090,6 +10752,8 @@ Count of unique users per week who delete an approval rule to a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9102,6 +10766,8 @@ Count of unique users per month who delete an approval rule to a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9114,6 +10780,8 @@ Count of unique users per week who edit an approval rule to a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9126,6 +10794,8 @@ Count of unique users per month who approve a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9138,6 +10808,8 @@ Count of unique users per week who approve a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9150,6 +10822,8 @@ Count of unique users per month who are assigned to a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9162,6 +10836,8 @@ Count of unique users per week who are assigned to a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9174,6 +10850,8 @@ Count of unique users per month who changed assignees of a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9186,6 +10864,8 @@ Count of unique users per week who changed assignees of a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9198,6 +10878,8 @@ Count of unique users per month who closed a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9210,6 +10892,8 @@ Count of unique users per week who closed a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9222,6 +10906,8 @@ Count of unique users per month who commented on a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9234,6 +10920,8 @@ Count of unique users per week who commented on a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9246,6 +10934,8 @@ Count of unique users per month who create a merge request from an issue Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9258,6 +10948,8 @@ Count of unique users per week who create a merge request from an issue Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9270,6 +10962,8 @@ Count of unique users per month who created a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9282,6 +10976,8 @@ Count of unique users per week who created a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9294,6 +10990,8 @@ Count of unique users per month who create a multiline comment in a merge reques Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9306,6 +11004,8 @@ Count of unique users per week who create a multiline comment in a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9318,6 +11018,8 @@ Count of unique users per month who create a note as part of a merge request rev Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9330,6 +11032,8 @@ Count of unique users per week who create a note as part of a merge request revi Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9342,6 +11046,8 @@ Count of unique users per month who edited a comment on a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9354,6 +11060,8 @@ Count of unique users per week who edited a comment on a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9366,6 +11074,8 @@ Count of unique users per week who edit a multiline comment in a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9378,6 +11088,8 @@ Count of unique users per week who edit a multiline comment in a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9390,6 +11102,8 @@ Count of unique users per month who changed labels of a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9402,6 +11116,8 @@ Count of unique users per week who changed labels of a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9414,6 +11130,8 @@ Count of unique users per week who load the conflict resolution page Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9426,6 +11144,8 @@ Count of unique users per week who load the conflict resolution page Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9438,6 +11158,8 @@ Count of unique users per month who mark a merge request as a draft Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9450,6 +11172,8 @@ Count of unique users per week who mark a merge request as a draft Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9462,6 +11186,8 @@ Count of unique users per month who merged a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9474,6 +11200,8 @@ Count of unique users per week who merged a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9486,6 +11214,8 @@ Count of unique users per month who changed milestone of a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9498,6 +11228,8 @@ Count of unique users per week who changed milestone of a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9510,6 +11242,8 @@ Count of unique users per month who locked a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9522,6 +11256,8 @@ Count of unique users per week who locked a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9534,6 +11270,8 @@ Count of unique users per month who unlocked a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9546,6 +11284,8 @@ Count of unique users per week who unlocked a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9558,6 +11298,8 @@ Count of unique users per month who publish their review as part of a merge requ Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9570,6 +11312,8 @@ Count of unique users per week who publish their review as part of a merge reque Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9582,6 +11326,8 @@ Count of unique users per month who removed a comment on a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9594,6 +11340,8 @@ Count of unique users per month who removed a comment on a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9606,6 +11354,8 @@ Count of unique users per month who remove a multiline comment in a merge reques Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9618,6 +11368,8 @@ Count of unique users per week who remove a multiline comment in a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9630,6 +11382,8 @@ Count of unique users per month who reopened a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9642,6 +11396,8 @@ Count of unique users per week who reopened a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9654,6 +11410,8 @@ Count of unique users per week who attempt to resolve a conflict through the ui Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9666,6 +11424,8 @@ Count of unique users per week who attempt to resolve a conflict through the ui Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9678,6 +11438,8 @@ Count of unique users per month who resolve a thread in a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9690,6 +11452,8 @@ Count of unique users per week who resolve a thread in a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9702,6 +11466,8 @@ Count of unique users per month who request a review of a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9714,6 +11480,8 @@ Count of unique users per week who request a review of a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9726,6 +11494,8 @@ Count of unique users per month who changed reviewers of a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9738,6 +11508,8 @@ Count of unique users per week who changed reviewers of a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9750,6 +11522,8 @@ Count of unique users per month with diffs viewed file by file Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9762,6 +11536,8 @@ Count of unique users per week with diffs viewed file by file Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9774,6 +11550,8 @@ Count of unique users per month who changed time estimate of a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9786,6 +11564,8 @@ Count of unique users per week who changed time estimate of a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9798,6 +11578,8 @@ Count of unique users per month who changed time spent on a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9810,6 +11592,8 @@ Count of unique users per week who changed time spent on a MR Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9822,6 +11606,8 @@ Count of unique users per month who toggled a task item in a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9834,6 +11620,8 @@ Count of unique users per week who toggled a task item in a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9846,6 +11634,8 @@ Count of unique users per month who unapprove a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9858,6 +11648,8 @@ Count of unique users per week who unapprove a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9870,6 +11662,8 @@ Count of unique users per month who unmark a merge request as a draft Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9882,6 +11676,8 @@ Count of unique users per week who unmark a merge request as a draft Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9894,6 +11690,8 @@ Count of unique users per month who unresolve a thread in a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9906,6 +11704,8 @@ Count of unique users per week who unresolve a thread in a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9918,6 +11718,8 @@ Count of unique users per month who use GitLab Workflow for VS Code Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -9930,153 +11732,179 @@ Count of unique users per week who use GitLab Workflow for VS Code Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.compliance.a_compliance_audit_events_api_monthly` -Missing description +Unique users that have used the Audit Events API in a given month. -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183942_a_compliance_audit_events_api_monthly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210216183942_a_compliance_audit_events_api_monthly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `redis_hll_counters.compliance.a_compliance_audit_events_api_weekly` -Missing description +Unique users that have used the Audit Events API in a given week. [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216183940_a_compliance_audit_events_api_weekly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `premium`, `ultimate` ### `redis_hll_counters.compliance.compliance_total_unique_counts_monthly` -Missing description +Unique count of compliance actions in a given month -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183946_compliance_total_unique_counts_monthly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210216183946_compliance_total_unique_counts_monthly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `redis_hll_counters.compliance.compliance_total_unique_counts_weekly` -Missing description +Unique count of compliance actions in a given week [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216183944_compliance_total_unique_counts_weekly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `premium`, `ultimate` ### `redis_hll_counters.compliance.g_compliance_audit_events_monthly` -Missing description +Unique users who have viewed the audit event screen in a given month. -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183930_g_compliance_audit_events_monthly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210216183930_g_compliance_audit_events_monthly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `redis_hll_counters.compliance.g_compliance_audit_events_weekly` -Missing description +Number of unique visitors to group-level audit events screen in a given week [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216183928_g_compliance_audit_events_weekly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `premium`, `ultimate` ### `redis_hll_counters.compliance.g_compliance_dashboard_monthly` -Missing description +Unique users who have viewed the compliance dashboard in a given month. -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183926_g_compliance_dashboard_monthly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210216183926_g_compliance_dashboard_monthly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `redis_hll_counters.compliance.g_compliance_dashboard_weekly` -Missing description +Unique users who have looked at the compliance dashboard in a given week [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216183924_g_compliance_dashboard_weekly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `premium`, `ultimate` ### `redis_hll_counters.compliance.i_compliance_audit_events_monthly` -Missing description +Unique users that have viewed the instance-level audit events screen -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183934_i_compliance_audit_events_monthly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210216183934_i_compliance_audit_events_monthly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `redis_hll_counters.compliance.i_compliance_audit_events_weekly` -Missing description +Unique users that have viewed the instance-level audit events screen [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216183932_i_compliance_audit_events_weekly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `premium`, `ultimate` ### `redis_hll_counters.compliance.i_compliance_credential_inventory_monthly` -Missing description +Unique users who have viewed the credential inventory in a given month. -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216183938_i_compliance_credential_inventory_monthly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210216183938_i_compliance_credential_inventory_monthly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `ultimate` ### `redis_hll_counters.compliance.i_compliance_credential_inventory_weekly` -Missing description +Unique visitors to the credential inventory screen in a given week [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216183936_i_compliance_credential_inventory_weekly.yml) -Group: `` +Group: `group::compliance` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `ultimate` ### `redis_hll_counters.deploy_token_packages.deploy_token_packages_total_unique_counts_monthly` @@ -10086,6 +11914,8 @@ A monthly count of packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10098,6 +11928,8 @@ A weekly count of packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10110,6 +11942,8 @@ A monthly count of Composer packages published to the registry using a deploy to Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10122,6 +11956,8 @@ A weekly count of Composer packages published to the registry using a deploy tok Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -10134,6 +11970,8 @@ A monthly count of Conan packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10146,6 +11984,8 @@ A weekly count of Conan packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10158,6 +11998,8 @@ A monthly count of container images published to the registry using a deploy tok Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -10170,6 +12012,8 @@ A weekly count of container images published to the registry using a deploy toke Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -10182,6 +12026,8 @@ A monthly count of Debian packages published to the registry using a deploy toke Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -10194,6 +12040,8 @@ A weekly count of Debian packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -10206,6 +12054,8 @@ A monthly count of generic packages published to the registry using a deploy tok Group: `group::package` +Data Category: `Optional` + Status: `broken` Tiers: `free`, `premium`, `ultimate` @@ -10218,6 +12068,8 @@ A weekly count of generic packages published to the registry using a deploy toke Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10230,6 +12082,8 @@ A monthly count of Go modules published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -10242,6 +12096,8 @@ A weekly count of Go modules published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -10254,6 +12110,8 @@ Distinct Helm pakages deployed in recent 28 days Group: `group::package` +Data Category: `Optional` + Status: `implemented` Tiers: `free`, `premium`, `ultimate` @@ -10266,6 +12124,8 @@ Distinct Helm pakages deployed in recent 7 days Group: `group::package` +Data Category: `Optional` + Status: `implemented` Tiers: `free`, `premium`, `ultimate` @@ -10278,6 +12138,8 @@ A monthly count of Maven packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10290,6 +12152,8 @@ A weekly count of Maven packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10302,6 +12166,8 @@ A monthly count of npm packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10314,6 +12180,8 @@ A weekly count of npm packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10326,6 +12194,8 @@ A monthly count of NuGet packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10338,6 +12208,8 @@ A weekly count of NuGet packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10350,6 +12222,8 @@ A monthly count of PyPI packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10362,6 +12236,8 @@ A weekly count of Python packages published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10374,6 +12250,8 @@ Distinct count events for RubyGems packages published using a Deploy token in re Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10386,6 +12264,8 @@ A weekly count of distinct RubyGems packages published using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10398,6 +12278,8 @@ A monthly count of package tags published to the registry using a deploy token Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -10410,6 +12292,8 @@ A weekly count of users that have published a package tag to the registry using Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -10422,6 +12306,8 @@ Number of distinct users authorized via deploy token creating Terraform Module p Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10434,6 +12320,8 @@ Number of distinct users authorized via deploy token creating Terraform Module p Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10446,6 +12334,8 @@ Number of users performing actions on Jira issues by month Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10458,6 +12348,8 @@ Number of users performing actions on Jira issues by week Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10470,6 +12362,8 @@ Number of users closing Jira issues by month Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10482,6 +12376,8 @@ Number of users closing Jira issues by week Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10494,6 +12390,8 @@ Number of users creating Jira issues by month Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10506,6 +12404,8 @@ Number of users creating Jira issues by week Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10518,6 +12418,8 @@ Number of users that cross-referenced Jira issues by month Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10530,6 +12432,8 @@ Number of users that cross-referenced Jira issues by week Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10542,6 +12446,8 @@ Count of Jira Issue List visits by month Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10554,6 +12460,8 @@ Count of Jira Issue List visits by week Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10566,6 +12474,8 @@ Calculated unique users to trigger a Slack message by performing an action on a Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10578,6 +12488,8 @@ Calculated unique users to trigger a Slack message by performing an action on a Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10590,6 +12502,8 @@ Calculated unique users to trigger a Slack message by creating a confidential no Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10602,6 +12516,8 @@ Calculated unique users to trigger a Slack message by creating a confidential no Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10614,6 +12530,8 @@ Calculated unique users to trigger a Slack message by performing a deployment by Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10626,6 +12544,8 @@ Calculated unique users to trigger a Slack message by performing a deployment by Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10638,6 +12558,8 @@ Calculated unique users to trigger a Slack message by performing an action on an Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10650,6 +12572,8 @@ Calculated unique users to trigger a Slack message by performing an action on an Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10662,6 +12586,8 @@ Calculated unique users to trigger a Slack message by performing an action on a Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10674,6 +12600,8 @@ Calculated unique users to trigger a Slack message by performing an action on a Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10686,6 +12614,8 @@ Calculated unique users to trigger a Slack message by creating a note by month Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10698,6 +12628,8 @@ Calculated unique users to trigger a Slack message by creating a note by week Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10710,6 +12642,8 @@ Calculated unique users to trigger a Slack message by performing a Git push by m Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10722,6 +12656,8 @@ Calculated unique users to trigger a Slack message by performing a Git push by w Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10734,6 +12670,8 @@ Calculated unique users to trigger a Slack message by performing a tag push by m Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10746,6 +12684,8 @@ Calculated unique users to trigger a Slack message by performing a tag push by w Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10758,6 +12698,8 @@ Calculated unique users to trigger a Slack message by performing an action on a Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10770,6 +12712,8 @@ Calculated unique users to trigger a Slack message by performing an action on a Group: `group::ecosystem` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -10782,6 +12726,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -10794,6 +12740,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -10806,6 +12754,8 @@ Count of MAU creating epic boards Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10818,6 +12768,8 @@ Count of WAU creating epic boards Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10830,6 +12782,8 @@ Count of MAU updating epic board names Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10842,6 +12796,8 @@ Count of WAU updating epic board names Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10854,6 +12810,8 @@ Count of MAU viewing epic boards Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10866,6 +12824,8 @@ Count of WAU viewing epic boards Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10878,6 +12838,8 @@ Total monthly users count for epics_usage Group: `group::product planning` +Data Category: `Operational` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10890,6 +12852,8 @@ Total weekly users count for epics_usage Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10902,6 +12866,8 @@ Counts of MAU closing epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10914,6 +12880,8 @@ Counts of WAU closing epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10926,6 +12894,8 @@ Count of MAU creating epics Group: `group::product planning` +Data Category: `Operational` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10938,6 +12908,8 @@ Count of WAU creating epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10950,6 +12922,8 @@ Count of MAU cross referencing epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10962,6 +12936,8 @@ Counts of WAU cross referencing epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10974,6 +12950,8 @@ Count of MAU destroying epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10986,6 +12964,8 @@ Count of WAU destroying epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -10998,6 +12978,8 @@ Count of MAU adding issues to epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11010,6 +12992,8 @@ Count of WAU adding issues to epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11022,6 +13006,8 @@ Counts of MAU moving epic issues between projects Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11034,6 +13020,8 @@ Counts of WAU moving epic issues between projects Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11046,6 +13034,8 @@ Count of MAU removing issues from epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11058,6 +13048,8 @@ Counts of WAU removing issues from epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11070,6 +13062,8 @@ Counts of MAU closing epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11082,6 +13076,8 @@ Counts of WAU re-opening epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11094,6 +13090,8 @@ Count of MAU chaging the epic lables Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11106,6 +13104,8 @@ Count of WAU chaging the epic lables Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11118,6 +13118,8 @@ Count of MAU promoting issues to epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11130,6 +13132,8 @@ Counts of WAU promoting issues to epics Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11142,6 +13146,8 @@ Counts of MAU awarding emoji on epic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11154,6 +13160,8 @@ Counts of WAU awarding emoji on epic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11166,6 +13174,8 @@ Counts of MAU adding epic notes Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11178,6 +13188,8 @@ Counts of WAU adding epic notes Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11190,6 +13202,8 @@ Counts of MAU destroying epic notes Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11202,6 +13216,8 @@ Counts of WAU destroying epic notes Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11214,6 +13230,8 @@ Number of users creating an issue from an epic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium` @@ -11226,6 +13244,8 @@ Number of users creating an issue from an epic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium` @@ -11238,6 +13258,8 @@ Counts of MAU removing emoji on epic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11250,6 +13272,8 @@ Counts of WAU removing emoji on epic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11262,6 +13286,8 @@ Count of MAU making epics confidential Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11274,6 +13300,8 @@ Count of WAU making epics confidential Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11286,6 +13314,8 @@ Counts of MAU setting epic due date as inherited Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11298,6 +13328,8 @@ Counts of WAU setting epic due date as fixed Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11310,6 +13342,8 @@ Counts of MAU setting epic due date as inherited Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11322,6 +13356,8 @@ Counts of WAU setting epic due date as inherited Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11334,6 +13370,8 @@ Counts of MAU setting epic start date as fixed Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11346,6 +13384,8 @@ Counts of WAU setting epic start date as fixed Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11358,6 +13398,8 @@ Counts of MAU setting epic start date as inherited Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11370,6 +13412,8 @@ Counts of WAU setting epic start date as inherited Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11382,6 +13426,8 @@ Count of MAU making epics visible Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11394,6 +13440,8 @@ Count of WAU making epics visible Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11406,6 +13454,8 @@ Counts of MAU changing epic descriptions Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11418,6 +13468,8 @@ Counts of WAU changing epic descriptions Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11430,6 +13482,8 @@ Counts of MAU updating epic notes Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11442,6 +13496,8 @@ Counts of WAU updating epic notes Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11454,6 +13510,8 @@ Counts of MAU updating parent on epic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11466,6 +13524,8 @@ Counts of WAU updating parent on epic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11478,6 +13538,8 @@ Counts of MAU changing epic titles Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11490,6 +13552,8 @@ Counts of WAU changing epic titles Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11502,6 +13566,8 @@ Counts of MAU manually updating fixed due date Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11514,6 +13580,8 @@ Counts of WAU manually updating fixed due date Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11526,6 +13594,8 @@ Counts of MAU manually updating fixed start date Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11538,6 +13608,8 @@ Counts of WAU manually updating fixed start date Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11550,6 +13622,8 @@ Counts of MAU checking epic task Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11562,6 +13636,8 @@ Counts of WAU checking epic task Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11574,6 +13650,8 @@ Counts of MAU unchecking epic task Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11586,6 +13664,8 @@ Counts of WAU unchecking epic task Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -11598,6 +13678,8 @@ Number of users editing a file from the single file editor Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -11610,6 +13692,8 @@ Weekly number of users editing from the single file editor Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -11622,6 +13706,8 @@ Count of monthly edits to a snippet Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -11634,6 +13720,8 @@ Weekly number of users editing Snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -11646,6 +13734,8 @@ Number of user editing files using the Static Site Editor Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -11658,6 +13748,8 @@ Weekly number of users editing using the Static Site Editor Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -11670,6 +13762,8 @@ Number of users editing a file from the Web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -11682,6 +13776,8 @@ Weekly number of users editing using the Web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -11694,6 +13790,8 @@ Count of unique users per month who edited a file from the Web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -11706,369 +13804,431 @@ Weekly number of users editing a file using the Web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_alert_assigned_monthly` -Missing description +Count of unique users assigning an alert per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180533_incident_management_alert_assigned_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_alert_assigned_weekly` -Missing description +Count of unique users assigning an alert per week -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180532_incident_management_alert_assigned_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180532_incident_management_alert_assigned_weekly.yml) + +Group: `group::monitor` -Group: `group::health` +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_alert_status_changed_monthly` -Missing description +Count of unique users changing alert's status changes per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180530_incident_management_alert_status_changed_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_alert_status_changed_weekly` -Missing description +Count of unique users changing alert's status per week + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180528_incident_management_alert_status_changed_weekly.yml) -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180528_incident_management_alert_status_changed_weekly.yml) +Group: `group::monitor` -Group: `group::health` +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_alert_todo_monthly` -Missing description +Count of unique users adding alerts to the TODO list per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180537_incident_management_alert_todo_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_alert_todo_weekly` -Missing description +Count of unique users adding alerts to the TODO list per week -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180535_incident_management_alert_todo_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180535_incident_management_alert_todo_weekly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_assigned_monthly` -Missing description +Count of users assigning incidents per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180552_incident_management_incident_assigned_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_assigned_weekly` -Missing description +Count of unique users assiging incidents per week + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180550_incident_management_incident_assigned_weekly.yml) -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180550_incident_management_incident_assigned_weekly.yml) +Group: `group::monitor` -Group: `group::health` +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_change_confidential_monthly` -Missing description +Count of users changing incidents to confidential per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180618_incident_management_incident_change_confidential_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_change_confidential_weekly` -Missing description +Count of unique users changing incidents to confidential per week -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180616_incident_management_incident_change_confidential_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180616_incident_management_incident_change_confidential_weekly.yml) + +Group: `group::monitor` -Group: `group::health` +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_closed_monthly` -Missing description +Count of users closing incidents per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180548_incident_management_incident_closed_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_closed_weekly` -Missing description +Count of users closing incidents per week -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180546_incident_management_incident_closed_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180546_incident_management_incident_closed_weekly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_comment_monthly` -Missing description +Count of unique users adding comments per month on incidents [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180559_incident_management_incident_comment_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_comment_weekly` -Missing description +Count of unique users adding comments on incidents per week -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180558_incident_management_incident_comment_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180558_incident_management_incident_comment_weekly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_created_monthly` -Missing description +Count of unique users creating incidents per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180541_incident_management_incident_created_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_created_weekly` -Missing description +Count of unique users creating incidents per week + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180539_incident_management_incident_created_weekly.yml) -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180539_incident_management_incident_created_weekly.yml) +Group: `group::monitor` -Group: `group::health` +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_published_monthly` -Missing description +Count of unique users that published incidents per month -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180607_incident_management_incident_published_monthly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210216180607_incident_management_incident_published_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_published_weekly` -Missing description +Count of unique users that published incidents per week [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180605_incident_management_incident_published_weekly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_relate_monthly` -Missing description +Count of unique users adding issues per month that are related to an incident [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180611_incident_management_incident_relate_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_relate_weekly` -Missing description +Count of unique users adding issues per that are related to an incident week -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180609_incident_management_incident_relate_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180609_incident_management_incident_relate_weekly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_reopened_monthly` -Missing description +Count of unique users reopening incidents per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180545_incident_management_incident_reopened_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_reopened_weekly` -Missing description +Count of unique users reopening incidents per week -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180543_incident_management_incident_reopened_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180543_incident_management_incident_reopened_weekly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_todo_monthly` -Missing description +Count of unique users adding incidents to the TODO list per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180556_incident_management_incident_todo_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_todo_weekly` -Missing description +Count of unique users adding incidents to the TODO list per week -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180554_incident_management_incident_todo_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180554_incident_management_incident_todo_weekly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_unrelate_monthly` -Missing description +Count of users removing issues that are related to an incident per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180614_incident_management_incident_unrelate_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_unrelate_weekly` -Missing description +Count of unique users removing issue that are related to an incident per week -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180612_incident_management_incident_unrelate_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180612_incident_management_incident_unrelate_weekly.yml) + +Group: `group::monitor` -Group: `group::health` +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_zoom_meeting_monthly` -Missing description +Count of users creating Zoom meetings about incidents per month + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180603_incident_management_incident_zoom_meeting_monthly.yml) -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210216180603_incident_management_incident_zoom_meeting_monthly.yml) +Group: `group::monitor` -Group: `group::health` +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_incident_zoom_meeting_weekly` -Missing description +Count of unique users creating Zoom meetings about incidents per week -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180601_incident_management_incident_zoom_meeting_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180601_incident_management_incident_zoom_meeting_weekly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_total_unique_counts_monthly` -Missing description +Count of unique users performing events related with incidents per month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180622_incident_management_total_unique_counts_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Operational` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management.incident_management_total_unique_counts_weekly` -Missing description +Count of unique users performing events related to the incident management -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180620_incident_management_total_unique_counts_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180620_incident_management_total_unique_counts_weekly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management_alerts.incident_management_alert_create_incident_monthly` @@ -12076,23 +14236,27 @@ Count of unique users per month to create an incident corresponding to an alert [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180625_incident_management_alert_create_incident_monthly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management_alerts.incident_management_alert_create_incident_weekly` Count of unique users per week to create an incident corresponding to an alert -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210216180623_incident_management_alert_create_incident_weekly.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216180623_incident_management_alert_create_incident_weekly.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: +Tiers: `free`, `premium`, `ultimate` ### `redis_hll_counters.incident_management_oncall.i_incident_management_oncall_notification_sent_monthly` @@ -12102,6 +14266,8 @@ Count of unique users to receive a notification while on-call Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12114,6 +14280,8 @@ Count of unique users to receive a notification while on-call Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12126,6 +14294,8 @@ Count of MAU adding an issue to an epic Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12138,6 +14308,8 @@ Count of WAU adding an issue to an epic Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12150,6 +14322,8 @@ Count of MAU changing issue assignees Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12162,6 +14336,8 @@ Count of WAU changing issue assignees Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12174,6 +14350,8 @@ Count of MAU changing the epic on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12186,6 +14364,8 @@ Count of WAU changing the epic on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12198,6 +14378,8 @@ Count of MAU cloning an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12210,6 +14392,8 @@ Count of WAU cloning an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12222,6 +14406,8 @@ Count of MAU closing an issue Group: `group::project management` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12234,6 +14420,8 @@ Count of WAU closing an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12246,6 +14434,8 @@ Count of MAU commenting on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12258,6 +14448,8 @@ Count of WAU commenting on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12270,6 +14462,8 @@ Count of MAU editing a comment on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12282,6 +14476,8 @@ Count of WAU editing a comment on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12294,6 +14490,8 @@ Count of MAU deleting a comment from an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12306,6 +14504,8 @@ Count of WAU deleting a comment from an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12318,6 +14518,8 @@ Count of MAU creating new issues Group: `group::project management` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12330,6 +14532,8 @@ Count of WAU creating issues Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12342,6 +14546,8 @@ Count of MAU referencing an issue from somewhere else Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12354,6 +14560,8 @@ Count of WAU referencing an issue from somewhere else Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12366,6 +14574,8 @@ Count of MAU editing an issue description Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12378,6 +14588,8 @@ Count of WAU editing an issue description Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12390,6 +14602,8 @@ Count of MAU adding a design to an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12402,6 +14616,8 @@ Count of WAU adding a design to an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12414,6 +14630,8 @@ Count of MAU modifying a design on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12426,6 +14644,8 @@ Count of WAU modifying a design on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12438,6 +14658,8 @@ Count of MAU removing a design from an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12450,6 +14672,8 @@ Count of WAU removing a design from an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12462,6 +14686,8 @@ Count of MAU changing an issue due date Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12474,6 +14700,8 @@ Count of WAU changing an issue due date Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12486,6 +14714,8 @@ Count of MAU changing the health status on an issue Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -12498,6 +14728,8 @@ Count of WAU changing the health status on an issue Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -12510,6 +14742,8 @@ Count of MAU changing an issue's iteration Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12522,6 +14756,8 @@ Count of WAU changing an issue's iteration Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12534,6 +14770,8 @@ Count of MAU changing an issue's label Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12546,6 +14784,8 @@ Count of WAU changing an issue's label Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12558,6 +14798,8 @@ Count of MAU locking an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12570,6 +14812,8 @@ Count of WAU locking an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12582,6 +14826,8 @@ Count of MAU making an issue confidential Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12594,6 +14840,8 @@ Count of WAU making an issue confidential Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12606,6 +14854,8 @@ Count of MAU making an issue not confidential Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12618,6 +14868,8 @@ Count of WAU making an issue not confidential Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12630,6 +14882,8 @@ Count of MAU marking an issue as a duplicate Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12642,6 +14896,8 @@ Count of WAU marking an issue as a duplicate Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12654,6 +14910,8 @@ Count of MAU changing an issue's milestone Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12666,6 +14924,8 @@ Count of WAU changing an issue's milestone Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12678,6 +14938,8 @@ Count of MAU moving an issue to another project Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12690,6 +14952,8 @@ Count of WAU moving an issue to another project Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12702,6 +14966,8 @@ Count of MAU relating an issue to another issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12714,6 +14980,8 @@ Count of WAU relating an issue to another issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12726,6 +14994,8 @@ Count of MAU removing an issue from an epic Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12738,6 +15008,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -12750,6 +15022,8 @@ Count of MAU re-opening a closed issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12762,6 +15036,8 @@ Count of WAU re-opening a closed issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12774,6 +15050,8 @@ Count of MAU changing an issue time estimate Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12786,6 +15064,8 @@ Count of WAU changing an issue time estimate Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12798,6 +15078,8 @@ Count of MAU recording time spent on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12810,6 +15092,8 @@ Count of WAU recording time spent on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12822,6 +15106,8 @@ Count of MAU editing an issue title Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12834,6 +15120,8 @@ Count of WAU editing an issue title Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12846,6 +15134,8 @@ Count of MAU unlocking an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12858,6 +15148,8 @@ Count of WAU unlocking an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12870,6 +15162,8 @@ Count of MAU unrelating an issue to another issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12882,6 +15176,8 @@ Count of WAU unrelating an issue to another issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12894,6 +15190,8 @@ Count of MAU changing an issue's weight Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12906,6 +15204,8 @@ Count of WAU changing an issue's weight Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -12918,6 +15218,8 @@ Aggregate count of MAU taking an action related to an issue Group: `group::project management` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12930,10 +15232,40 @@ Aggregate count of WAU taking an action related to an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` +### `redis_hll_counters.network_policies.clusters_using_network_policies_ui_monthly` + +Monthly number of distinct clusters with network policies using the network policies UI + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210623202402_clusters_using_network_policies_ui_monthly.yml) + +Group: `group::container security` + +Data Category: `Operational` + +Status: `implemented` + +Tiers: `ultimate` + +### `redis_hll_counters.network_policies.clusters_using_network_policies_ui_weekly` + +Weekly number of distinct clusters with network policies using the network policies UI + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_7d/20210623202358_clusters_using_network_policies_ui_weekly.yml) + +Group: `group::container security` + +Data Category: `Operational` + +Status: `implemented` + +Tiers: `ultimate` + ### `redis_hll_counters.pipeline_authoring.o_pipeline_authoring_unique_users_committing_ciconfigfile_monthly` Monthly unique user count doing commits which contains the CI config file @@ -12942,6 +15274,8 @@ Monthly unique user count doing commits which contains the CI config file Group: `group::pipeline authoring` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12954,6 +15288,8 @@ Weekly unique user count doing commits which contains the CI config file Group: `group::pipeline authoring` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12966,6 +15302,8 @@ Monthly unique user count having merge requests which contains the CI config fil Group: `group::pipeline authoring` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12978,6 +15316,8 @@ Weekly unique user count having merge requests which contains the CI config file Group: `group::pipeline authoring` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -12990,6 +15330,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13002,6 +15344,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13014,6 +15358,8 @@ Count of MAU using the `/approve` quick action Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13026,6 +15372,8 @@ Count of WAU using the `/approve` quick action Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13038,6 +15386,8 @@ Count of MAU using the `/assign @user1 @user2` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13050,6 +15400,8 @@ Count of WAU using the `/assign @user1 @user2` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13062,6 +15414,8 @@ Count of MAU using the `/assign_reviewer` or `request_reviewer` quick action Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13074,6 +15428,8 @@ Count of WAU using the `/assign_reviewer` or `request_reviewer` quick action Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13086,6 +15442,8 @@ Count of MAU using the `/assign me` quick action to assign self to an issuable Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13098,6 +15456,8 @@ Count of WAU using the `/assign me` quick action to assign self to an issuable Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13110,6 +15470,8 @@ Count of MAU using the `/assign @user1` quick action to assign a single individu Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13122,6 +15484,8 @@ Count of WAU using the `/assign @user1` quick action to assign a single individu Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13134,6 +15498,8 @@ Count of MAU using the `/award` quick action to set an award emoji on an issuabl Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13146,6 +15512,8 @@ Count of WAU using the `/award` quick action to set an award emoji on an issuabl Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13158,6 +15526,8 @@ Count of MAU using the `/board_move` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13170,6 +15540,8 @@ Count of WAU using the `/board_move` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13182,6 +15554,8 @@ Count of MAU using the `/child_epic` quick action Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -13194,6 +15568,8 @@ Count of WAU using the `/child_epic` quick action Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -13206,6 +15582,8 @@ Count of MAU using the `/clear_weight` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13218,6 +15596,8 @@ Count of WAU using the `/clear_weight` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13230,6 +15610,8 @@ Count of MAU using the `/clone` quick action to clone an issue. Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13242,6 +15624,8 @@ Count of WAU using the `/clone` quick action to clone an issue. Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13254,6 +15638,8 @@ Count of MAU using the `/close` quick action to close an issuable Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13266,6 +15652,8 @@ Count of WAU using the `/close` quick action to close an issuable Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13278,6 +15666,8 @@ Count of MAU using the `/confidential` quick action to set an issue as confident Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13290,6 +15680,8 @@ Count of WAU using the `/confidential` quick action to set an issue as confident Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13302,6 +15694,8 @@ Count of MAU using the `/copy_metadata` quick action on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13314,6 +15708,8 @@ Count of WAU using the `/copy_metadata` quick action on an issue Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13326,6 +15722,8 @@ Count of MAU using the `/copy_metadata` quick action on a Merge Request Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13338,6 +15736,8 @@ Count of WAU using the `/copy_metadata` quick action on a Merge Request Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13350,6 +15750,8 @@ Count of MAU using the `/create_merge_request` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13362,6 +15764,8 @@ Count of WAU using the `/create_merge_request` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13374,6 +15778,8 @@ Count of MAU using the `/done` quick action to mark a todo as done Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13386,6 +15792,8 @@ Count of WAU using the `/done` quick action to mark a todo as done Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13398,6 +15806,8 @@ Count of MAU using the `/draft` quick action on a Merge Request Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13410,6 +15820,8 @@ Count of WAU using the `/draft` quick action on a Merge Request Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13422,6 +15834,8 @@ Count of MAU using the `/due` quick action to change the due date on an issuable Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13434,6 +15848,8 @@ Count of WAU using the `/due` quick action to change the due date on an issuable Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13446,6 +15862,8 @@ Count of MAU using the `/duplicate` quick action to mark an issue as a duplicate Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13458,6 +15876,8 @@ Count of WAU using the `/duplicate` quick action to mark an issue as a duplicate Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13470,6 +15890,8 @@ Count of MAU using the `/epic` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13482,6 +15904,8 @@ Count of WAU using the `/epic` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13494,6 +15918,8 @@ Count of MAU using the `/estimate` quick action to set a time estimate on an iss Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13506,6 +15932,8 @@ Count of WAU using the `/estimate` quick action to set a time estimate on an iss Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13518,6 +15946,8 @@ Unique users using the /invite_email quick action to add a multiple email partic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13530,6 +15960,8 @@ Unique users using the /invite_email quick action to add a multiple email partic Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13542,6 +15974,8 @@ Unique users using the /invite_email quick action to add a single email particip Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13554,6 +15988,8 @@ Unique users using the /invite_email quick action to add a single email particip Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13566,6 +16002,8 @@ Count of MAU using the `/iteration` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13578,6 +16016,8 @@ Count of WAU using the `/iteration` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13590,6 +16030,8 @@ Count of MAU using the `/label` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13602,6 +16044,8 @@ Count of WAU using the `/label` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13614,6 +16058,8 @@ Count of MAU using the `/lock` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13626,6 +16072,8 @@ Count of WAU using the `/lock` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13638,6 +16086,8 @@ Count of MAU using the `/merge` quick action Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13650,6 +16100,8 @@ Count of WAU using the `/merge` quick action Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13662,6 +16114,8 @@ Count of MAU using the `/milestone` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13674,6 +16128,8 @@ Count of WAU using the `/milestone` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13686,6 +16142,8 @@ Count of MAU using the `/move` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13698,6 +16156,8 @@ Count of WAU using the `/move` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13710,6 +16170,8 @@ Count of MAU using the `/parent_epic` quick action Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -13722,6 +16184,8 @@ Count of WAU using the `/parent_epic` quick action Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -13734,6 +16198,8 @@ Count of MAU using the `/promote` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13746,6 +16212,8 @@ Count of WAU using the `/promote` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13758,6 +16226,8 @@ Count of MAU using the `/publish` quick action Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -13770,6 +16240,8 @@ Count of WAU using the `/publish` quick action Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -13782,6 +16254,8 @@ Count of MAU using the `/reassign @user1` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13794,6 +16268,8 @@ Count of MAU using the `/reassign_reviewer` quick action Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13806,6 +16282,8 @@ Count of WAU using the `/reassign_reviewer` quick action Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13818,6 +16296,8 @@ Count of WAU using the `/reassign @user1` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13830,6 +16310,8 @@ Count of MAU using the `/rebase` quick action on a Merge Request Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13842,6 +16324,8 @@ Count of WAU using the `/rebase` quick action on a Merge Request Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13854,6 +16338,8 @@ Count of MAU using the `/relabel` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13866,6 +16352,8 @@ Count of WAU using the `/relabel` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13878,6 +16366,8 @@ Count of MAU using the `/relate` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13890,6 +16380,8 @@ Count of WAU using the `/relate` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13902,6 +16394,8 @@ Count of MAU using the `/remove_child_epic` quick action Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -13914,6 +16408,8 @@ Count of WAU using the `/remove_child_epic` quick action Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -13926,6 +16422,8 @@ Count of MAU using the `/remove_due_date` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13938,6 +16436,8 @@ Count of WAU using the `/remove_due_date` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13950,6 +16450,8 @@ Count of MAU using the `/remove_epic` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13962,6 +16464,8 @@ Count of WAU using the `/remove_epic` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -13974,6 +16478,8 @@ Count of MAU using the `/remove_estimate` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13986,6 +16492,8 @@ Count of WAU using the `/remove_estimate` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -13998,6 +16506,8 @@ Count of MAU using the `/remove_iteration` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14010,6 +16520,8 @@ Count of WAU using the `/remove_iteration` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14022,6 +16534,8 @@ Count of MAU using the `/remove_milestone` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14034,6 +16548,8 @@ Count of WAU using the `/remove_milestone` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14046,6 +16562,8 @@ Count of MAU using the `/remove_parent_epic` quick action Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -14058,6 +16576,8 @@ Count of WAU using the `/remove_parent_epic` quick action Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -14070,6 +16590,8 @@ Count of MAU using the `/remove_time_spent` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14082,6 +16604,8 @@ Count of WAU using the `/remove_time_spent` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14094,6 +16618,8 @@ Count of MAU using the `/remove_zoom` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14106,6 +16632,8 @@ Count of WAU using the `/remove_zoom` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14118,6 +16646,8 @@ Count of MAU using the `/reopen` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14130,6 +16660,8 @@ Count of WAU using the `/reopen` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14142,6 +16674,8 @@ Count of MAU using the `/shrug` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14154,6 +16688,8 @@ Count of WAU using the `/shrug` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14166,6 +16702,8 @@ Count of MAU using the `/spend` quick action to add time spent Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14178,6 +16716,8 @@ Count of WAU using the `/spend` quick action to add time spent Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14190,6 +16730,8 @@ Count of MAU using the `/spend` quick action to subtract time spent Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14202,6 +16744,8 @@ Count of WAU using the `/spend` quick action to subtract time spent Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14214,6 +16758,8 @@ Count of MAU using the `/submit_review` quick action on Merge Requests Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14226,6 +16772,8 @@ Count of WAU using the `/submit_review` quick action on Merge Requests Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14238,6 +16786,8 @@ Count of MAU using the `/subscribe` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14250,6 +16800,8 @@ Count of WAU using the `/subscribe` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14262,6 +16814,8 @@ Count of MAU using the `/tableflip` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14274,6 +16828,8 @@ Count of WAU using the `/tableflip` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14286,6 +16842,8 @@ Count of MAU using the `/tag` quick action Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14298,6 +16856,8 @@ Count of WAU using the `/tag` quick action Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14310,6 +16870,8 @@ Count of MAU using the `/target_branch` quick action on Merge Requests Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14322,6 +16884,8 @@ Count of WAU using the `/target_branch` quick action on Merge Requests Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14334,6 +16898,8 @@ Count of MAU using the `/title` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14346,6 +16912,8 @@ Count of WAU using the `/title` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14358,6 +16926,8 @@ Count of MAU using the `/todo` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14370,6 +16940,8 @@ Count of WAU using the `/todo` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14382,6 +16954,8 @@ Count of MAU using the `/unassign` quick action on Merge Requests Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14394,6 +16968,8 @@ Count of WAU using the `/unassign` quick action on Merge Requests Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14406,6 +16982,8 @@ Count of MAU using the `/unassign_reviewer` or `/remove_reviewer` quick action o Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14418,6 +16996,8 @@ Count of WAU using the `/unassign_reviewer` or `/remove_reviewer` quick action o Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14430,6 +17010,8 @@ Count of MAU using the `/unassign @user1` quick action on Merge Requests Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14442,6 +17024,8 @@ Count of WAU using the `/unassign @user1` quick action on Merge Requests Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14454,6 +17038,8 @@ Count of MAU using the `/unlabel` quick action to remove all labels Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14466,6 +17052,8 @@ Count of WAU using the `/unlabel` quick action to remove all labels Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14478,6 +17066,8 @@ Count of MAU using the `/unlabel` or `/remove_label` quick action to remove one Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14490,6 +17080,8 @@ Count of WAU using the `/unlabel` or `/remove_label` quick action to remove one Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14502,6 +17094,8 @@ Count of MAU using the `/unlock` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14514,6 +17108,8 @@ Count of WAU using the `/unlock` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14526,6 +17122,8 @@ Count of MAU using the `/unsubscribe` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14538,6 +17136,8 @@ Count of WAU using the `/unsubscribe` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14550,6 +17150,8 @@ Count of MAU using the `/weight` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14562,6 +17164,8 @@ Count of WAU using the `/weight` quick action Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14574,6 +17178,8 @@ Count of MAU using the `/wip` quick action on Merge Requests Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14586,6 +17192,8 @@ Count of WAU using the `/wip` quick action on Merge Requests Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14598,6 +17206,8 @@ Count of MAU using the `/zoom` quick action on Issues Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14610,6 +17220,8 @@ Count of WAU using the `/zoom` quick action on Issues Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14622,6 +17234,8 @@ Count of MAU using one or more quick actions Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14634,6 +17248,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -14646,6 +17262,8 @@ Calculated unique users to perform Advanced searches by month Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14658,6 +17276,8 @@ Calculated unique users to perform Advanced searches by week Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14670,6 +17290,8 @@ Calculated unique users to perform a search with a paid license enabled by month Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14682,6 +17304,8 @@ Calculated unique users to perform a search with a paid license enabled by week Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14694,6 +17318,8 @@ Calculated unique users to perform Basic or Advanced searches by month Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14706,6 +17332,8 @@ Calculated unique users to perform Basic or Advanced searches by week Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14718,6 +17346,8 @@ Total unique users for i_search_total, i_search_advanced, i_search_paid for rece Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14730,6 +17360,8 @@ Calculated unique users to perform Basic or Advanced searches by week Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14742,6 +17374,8 @@ Count of expanding the security report widget Group: `group::static analysis` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14754,6 +17388,8 @@ Count of expanding the security report widget Group: `group::static analysis` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14766,6 +17402,8 @@ Monthly number of users viewing snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14778,6 +17416,8 @@ Weekly number of users viewing snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14790,6 +17430,8 @@ Count of total design actions (upload, delete, comment, reply) Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14802,6 +17444,8 @@ Count of total design actions (upload, delete, comment, reply) Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14814,6 +17458,8 @@ Count of unique Git write actions Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14826,6 +17472,8 @@ Count of unique Git write actions Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14838,6 +17486,8 @@ Count of unique users who use code intelligence Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14850,6 +17500,8 @@ Count of unique users who use code intelligence Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14862,6 +17514,8 @@ Count of unique users who perform an action on a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14874,6 +17528,8 @@ Count of unique users who perform an action on a merge request Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14886,6 +17542,8 @@ Count of unique actions done on projects and related resources (create, edit, de Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14898,6 +17556,8 @@ Count of unique actions done on projects and related resources (create, edit, de Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14910,6 +17570,8 @@ Count of unique actions done on a wiki (create, edit, delete) Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14922,6 +17584,8 @@ Count of unique actions done on a wiki (create, edit, delete) Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14934,6 +17598,8 @@ Monthly active users of GitLab Managed Terraform states Group: `group::configure` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -14946,6 +17612,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -14958,6 +17626,8 @@ Count of unique users per week|month who visit the full code quality report Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14970,6 +17640,8 @@ Count of unique users per week who visit the full code quality report Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14982,6 +17654,8 @@ Aggregated count of unique users who have clicked from group code coverage page Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -14994,6 +17668,8 @@ Aggregated count of unique users who have clicked from group code coverage page Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15006,6 +17682,8 @@ Count of unique users per month who visited the group code coverage page Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15018,6 +17696,8 @@ Count of unique users per week who visited the group code coverage page Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15030,6 +17710,8 @@ Count of unique users per month who expanded the load performance report MR widg Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15042,6 +17724,8 @@ Count of unique users per week who expanded the load performance report MR widge Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15054,6 +17738,8 @@ Tracks number of metrics reports uploaded monthly. Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15066,6 +17752,8 @@ Count of unique users per week who trigger a pipeline that uploads a metrics rep Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15078,6 +17766,8 @@ Count of unique users per month who expanded the metrics report MR widget Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15090,6 +17780,8 @@ Count of unique users per week who expanded the metrics report MR widget Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15102,6 +17794,8 @@ Unique users that expand the test summary merge request widget by month Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15114,6 +17808,8 @@ Unique users that expand the test summary merge request widget by week Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15126,6 +17822,8 @@ Internal Tracking to count number of unit tests parsed for planning of future co Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15138,6 +17836,8 @@ Internal Tracking to count number of unit tests parsed for planning of future co Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15150,6 +17850,8 @@ Count of unique users per month who expanded the browser performance report MR w Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15162,6 +17864,8 @@ Count of unique users per week who expanded the browser performance report MR wi Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15174,6 +17878,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `removed` Tiers: `free` @@ -15186,6 +17892,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `removed` Tiers: `premium`, `ultimate` @@ -15198,6 +17906,8 @@ Count of expanding the accessibility report widget Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15210,6 +17920,8 @@ Count of expanding the accessibility report widget Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15222,6 +17934,8 @@ Count of expanding the code quality widget Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15234,6 +17948,8 @@ Count of expanding the code quality widget Group: `group::testing` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15246,6 +17962,8 @@ A monthly count of users that have published a Composer package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15258,6 +17976,8 @@ A weekly count of users that have published a Composer package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15270,6 +17990,8 @@ A monthly count of users that have published a Conan package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15282,6 +18004,8 @@ A weekly count of users that have published a Conan package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15294,6 +18018,8 @@ A monthly count of users that have published a container image to the registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -15306,6 +18032,8 @@ A weekly count of users that have published a container image to the registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -15318,6 +18046,8 @@ A monthly count of users that have published a Debian package to the registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -15330,6 +18060,8 @@ A weekly count of users that have published a Debian package to the registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -15342,6 +18074,8 @@ A monthly count of users that have published a generic package to the registry Group: `group::package` +Data Category: `Optional` + Status: `broken` Tiers: `free`, `premium`, `ultimate` @@ -15354,6 +18088,8 @@ A weekly count of users that have published a generic package to the registry Group: `group::package` +Data Category: `Optional` + Status: `broken` Tiers: `free`, `premium`, `ultimate` @@ -15366,6 +18102,8 @@ A monthly count of users that have published a Go moduleto the registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -15378,6 +18116,8 @@ A weekly count of users that have published a Go module to the registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -15390,6 +18130,8 @@ Distinct user count events for Helm packages in recent 28 days Group: `group::package` +Data Category: `Optional` + Status: `implemented` Tiers: `free`, `premium`, `ultimate` @@ -15402,6 +18144,8 @@ Distinct user count events for Helm packages in recent 7 days Group: `group::package` +Data Category: `Optional` + Status: `implemented` Tiers: `free`, `premium`, `ultimate` @@ -15414,6 +18158,8 @@ A monthly count of users that have published a Maven package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15426,6 +18172,8 @@ A weekly count of users that have published a Maven package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15438,6 +18186,8 @@ A monthly count of users that have published an npm package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15450,6 +18200,8 @@ A weekly count of users that have published an npm package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15462,6 +18214,8 @@ A monthly count of users that have published a NuGet package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15474,6 +18228,8 @@ A weekly count of users that have published a NuGet package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15486,6 +18242,8 @@ A monthly count of users that have published a PyPI package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15498,6 +18256,8 @@ A weekly count of users that have published a Python package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15510,6 +18270,8 @@ Distinct user count of RubyGems packages published in recent 28 days Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15522,6 +18284,8 @@ A weekly count of distinct RubyGems packages published by a user Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15534,6 +18298,8 @@ A monthly count of users that have published a package tag to the registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -15546,6 +18312,8 @@ A weekly count of users that have published a package with a tag to the registry Group: `group::package` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -15558,6 +18326,8 @@ Number of distinct users creating Terraform Module packages in recent 28 days Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15570,6 +18340,8 @@ Number of distinct users creating Terraform Module packages in recent 7 days Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15582,6 +18354,8 @@ A monthly count of users that have published a package to the registry Group: `group::package` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15594,6 +18368,8 @@ A weekly count of users that have published a package to the registry Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15606,6 +18382,8 @@ Whether incoming email is setup Group: `group::certify` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15618,6 +18396,8 @@ Calculated unique users to perform Advanced searches by week Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15630,6 +18410,8 @@ Calculated unique users to perform a search with a paid license enabled by week Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15642,6 +18424,8 @@ Calculated unique users to perform Basic or Advanced searches by week Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15654,6 +18438,8 @@ Total unique users for i_search_total, i_search_advanced, i_search_paid for rece Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15666,10 +18452,28 @@ Total unique users for i_search_total, i_search_advanced, i_search_paid for rece Group: `group::global search` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` +### `settings.collected_data_categories` + +List of collected data categories corresponding to instance settings + +[Object JSON schema](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/objects_schemas/collected_data_categories_schema.json) + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/settings/20210702140138_collected_data_categories.yml) + +Group: `group::product intelligence` + +Data Category: `Standard` + +Status: `implemented` + +Tiers: `free`, `premium`, `ultimate` + ### `settings.gitaly_apdex` Gitaly application performance @@ -15678,6 +18482,8 @@ Gitaly application performance Group: `group::gitaly` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15690,6 +18496,8 @@ Is encrypted LDAP secrets configured? Group: `group::distribution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15702,6 +18510,8 @@ Information about the operating system running GitLab Group: `group::distribution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15714,6 +18524,8 @@ Whether public signup is enabled Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15728,6 +18540,8 @@ Topology data Group: `group::memory` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15740,6 +18554,8 @@ Total GitLab Managed clusters with GitLab Managed App:Cert Manager installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15752,6 +18568,8 @@ Total GitLab Managed clusters with GitLab Managed App:Helm enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15764,6 +18582,8 @@ Total GitLab Managed clusters with GitLab Managed App:Ingress installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15776,6 +18596,8 @@ Total GitLab Managed clusters with GitLab Managed App:Knative installed Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15788,6 +18610,8 @@ Total GitLab Managed disabled clusters Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15800,6 +18624,8 @@ Total GitLab Managed clusters currently enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15812,6 +18638,8 @@ Total GitLab Managed clusters with defined cluster management project Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15824,6 +18652,8 @@ Total GitLab Managed clusters provisioned with GitLab on AWS EKS Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15836,6 +18666,8 @@ Total GitLab Managed clusters provisioned with GitLab on GCE GKE Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15848,6 +18680,8 @@ Total GitLab Managed clusters that are user provisioned Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15860,6 +18694,8 @@ Total GitLab Managed disabled clusters attached to groups Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15872,6 +18708,8 @@ Total GitLab Managed enabled clusters attached to groups Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15884,6 +18722,8 @@ Total GitLab Managed disabled clusters attached to the instance Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15896,6 +18736,8 @@ Total GitLab Managed enabled clusters attached to the instance Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15908,6 +18750,8 @@ Total GitLab Managed disabled clusters attached to projects Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15920,6 +18764,8 @@ Total GitLab Managed enabled clusters attached to projects Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -15932,6 +18778,8 @@ Unique projects with Slack webhook enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -15944,6 +18792,8 @@ Unique projects with Slack ‘/’ commands enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -15956,6 +18806,8 @@ Projects with Prometheus alerting enabled Group: `group::configure` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -15968,6 +18820,8 @@ Total number of project approval rules Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15980,6 +18834,8 @@ Number of approval rules with the exact number of required approvers. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -15992,6 +18848,8 @@ Number of approval rules with fewer approvers than required. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16004,6 +18862,8 @@ Number of approval rules with more approvers than required. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16016,6 +18876,8 @@ Number of project approval rules scoped to a specific repo branch. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16028,6 +18890,8 @@ Count of users creating deploy keys. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16040,6 +18904,8 @@ Count of users creating regular keys. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16052,6 +18918,8 @@ Count of the number of users creating merge requests Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16064,6 +18932,8 @@ Merge requests with added rules Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16076,6 +18946,8 @@ Count of merge requests with optional codeowner approval rules Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16088,6 +18960,8 @@ Number of merge requests that have overridden rules created at the project level Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16100,6 +18974,8 @@ Count of merge requests with required codeowner approval rules Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16112,6 +18988,8 @@ Count of users creating projects that require approval by code owners for code c Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16124,6 +19002,8 @@ Missing description Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -16136,6 +19016,8 @@ Total count of projects that do not allow overriding approvers on discrete merge Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16148,6 +19030,8 @@ Count of projects that have a matching Git repository, result of a Git push acti Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16160,6 +19044,8 @@ Count of projects using code owners with code owners section feature Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16172,6 +19058,8 @@ Count of total projects that do not disable overriding approvers per discrete me Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16184,6 +19072,8 @@ Count of users creating projects with repositories making use of at least one pr Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16196,6 +19086,8 @@ Count of users creating projects with remote mirrors. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16208,6 +19100,8 @@ Count of distinct author_id from snippets Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16220,6 +19114,8 @@ Count of unique users who create suggestions in merge request comments Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16232,6 +19128,8 @@ The total number of files which have been locked via the GitLab UI Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16244,6 +19142,8 @@ Number of paths/directories manually locked through the UI Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16256,6 +19156,8 @@ Number of unique users who have locked files or directories using LFS via the co Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16268,6 +19170,8 @@ Number of users who have manually locked paths/directories through the UI Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16280,6 +19184,8 @@ Number of Git fetch events from Prometheus on the Geo secondary Group: `group::geo` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16292,6 +19198,8 @@ Number of Git push events from Prometheus on the Geo secondary Group: `group::geo` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16304,6 +19212,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16316,6 +19226,8 @@ Distinct count of users that triggered an import using the Group Migration tool Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16328,10 +19240,26 @@ Count of imports using GitLab Migration Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free` +### `usage_activity_by_stage.manage.compliance_frameworks_with_pipeline` + +Count of compliance frameworks that have a pipeline configuration + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210622123800_compliance_frameworks_with_pipeline.yml) + +Group: `compliance` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `ultimate` + ### `usage_activity_by_stage.manage.custom_compliance_frameworks` Total count of all custom compliance framework labels @@ -16340,6 +19268,8 @@ Total count of all custom compliance framework labels Group: `compliance` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16352,6 +19282,8 @@ Missing description Group: `group::manage` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -16364,6 +19296,8 @@ Count of groups imported using GitLab Migration Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -16376,6 +19310,8 @@ Count of group imports using Group Import/Export Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -16388,6 +19324,8 @@ Has the instance enabled Group SAML SSO `https://docs.gitlab.com/ee/user/group/s Group: `group::manage` +Data Category: `Optional` + Status: `data_available` Tiers: `premium` @@ -16400,6 +19338,8 @@ Number of users who are group members. Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16412,6 +19352,8 @@ Distinct count of users that imported groups using Group Import Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16424,6 +19366,8 @@ Count of (attempted) imports from csv files Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -16436,6 +19380,8 @@ Count of projects imported from fogbugz Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -16448,6 +19394,8 @@ Count of projects imported from Jira Group: `group::import` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -16460,6 +19408,8 @@ Count of projects imported from phabricator Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -16472,6 +19422,8 @@ Distinct count of users that imported issues into projects using CSV upload Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16484,6 +19436,8 @@ Distinct count of users that imported issues into projects using FogBugz Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16496,6 +19450,8 @@ Distinct count of users that imported issues into projects using Jira Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16508,6 +19464,8 @@ Distinct count of users that imported issues into projects using Phabricator Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16520,6 +19478,8 @@ Has the instance configured [LDAP Admin Sync](https://docs.gitlab.com/ee/adminis Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16532,6 +19492,8 @@ Has the instance configured [LDAP Group Sync](https://docs.gitlab.com/ee/adminis Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16544,6 +19506,8 @@ Number of users creating keys synced as part of LDAP Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16556,6 +19520,8 @@ Number of [LDAP servers configured for the instance](https://docs.gitlab.com/ee/ Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16568,6 +19534,8 @@ Number of users that are linked to LDAP Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16580,6 +19548,8 @@ Number of unique user logins using an OmniAuth provider Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16592,6 +19562,8 @@ Count of projects imported from Bitbucket Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16604,6 +19576,8 @@ Count of projects imported from Bitbucket Server Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16616,6 +19590,8 @@ Count of projects imported by URL Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16628,6 +19604,8 @@ Count of projects imported from Gitea Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16640,6 +19618,8 @@ Count of projects imported from GitHub Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16652,6 +19632,8 @@ Count of projects imported from GitLab.com Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16664,6 +19646,8 @@ Count of projects imported using GitLab Migration Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16676,6 +19660,8 @@ Count of projects imported using Project Import/Export Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16688,6 +19674,8 @@ Count of projects imported using manifst file Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16700,6 +19688,8 @@ Count number of projects imported monthly Group: `group::import` +Data Category: `Optional` + Status: `implemented` Tiers: `free`, `premium`, `ultimate` @@ -16712,6 +19702,8 @@ Distinct count of users that imported projects from Bitbucket Cloud Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16724,6 +19716,8 @@ Distinct count of users that imported projects from Bitbucket Server Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16736,6 +19730,8 @@ Distinct count of users that imported projects using Import by URL Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16748,6 +19744,8 @@ Distinct count of users that imported projects from Gitea Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16760,6 +19758,8 @@ Distinct count of users that imported projects from GitHub Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16772,6 +19772,8 @@ Distinct count of users that imported projects from GitLab.com Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16784,6 +19786,8 @@ Distinct count of users that imported projects using Project Import/Export Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16796,6 +19800,8 @@ Distinct count of users that imported projects using Manifest file Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16808,6 +19814,8 @@ Total count of all projects imported with import_source NOT NULL Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -16820,6 +19828,8 @@ Number of projects labeled with a compliance framework label [see](https://gitla Group: `group::manage` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -16832,6 +19842,8 @@ Distinct count of users that triggered any kind of import Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -16844,6 +19856,8 @@ Number of unique user logins using Google OAuth authentication Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16856,6 +19870,8 @@ Number of unique user logins using password authentication Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16868,6 +19884,8 @@ Number of unique user logins using two factor authentication Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16880,6 +19898,8 @@ Number of unique user logins using two factor via a U2F device Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16892,6 +19912,8 @@ Number of unique user logins using two factor via a WebAuthn device Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16904,6 +19926,8 @@ Number of users Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16916,6 +19940,8 @@ Number of custom value stream analytics stages. Group: `group::optimize` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -16928,6 +19954,8 @@ Users creating clusters. Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16940,6 +19968,8 @@ Users creating clusters with Prometheus enabled. Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16952,6 +19982,8 @@ Active users with enabled operations dashboard Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium` @@ -16964,6 +19996,8 @@ Active users with projects on operations dashboard Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -16972,13 +20006,15 @@ Tiers: `free`, `premium`, `ultimate` Projects where Incident SLA is enabled -[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180522_projects_incident_sla_enabled.yml) +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216180522_projects_incident_sla_enabled.yml) + +Group: `group::monitor` -Group: `group::health` +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `premium`, `ultimate` ### `usage_activity_by_stage.monitor.projects_with_alert_incidents` @@ -16986,11 +20022,13 @@ Count of unique projects with an incident from an alert [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180520_projects_with_alert_incidents.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `usage_activity_by_stage.monitor.projects_with_enabled_alert_integrations_histogram` @@ -17002,6 +20040,8 @@ Histogram (buckets 1 to 100) of projects with at least 1 enabled integration. Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17012,11 +20052,13 @@ Projects where error tracking is enabled [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180517_projects_with_error_tracking_enabled.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `usage_activity_by_stage.monitor.projects_with_incidents` @@ -17024,11 +20066,13 @@ Count of unique projects with an incident [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216180518_projects_with_incidents.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `usage_activity_by_stage.monitor.projects_with_tracing_enabled` @@ -17038,6 +20082,8 @@ Projects with tracing enabled Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17050,6 +20096,8 @@ Projects with package registry enabled Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17062,6 +20110,8 @@ Count of users creating assignee lists on Boards Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -17074,6 +20124,8 @@ Missing description Group: `group::plan` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -17086,6 +20138,8 @@ Count of users creating Issues Group: `group::project management` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17098,6 +20152,8 @@ Count of users creating label lists on Boards Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17110,6 +20166,8 @@ Count of users creating milestone lists on Boards Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -17122,6 +20180,8 @@ Count of users creating Notes on Issues Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17134,6 +20194,8 @@ Count of users creating projects Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17146,6 +20208,8 @@ Missing description Group: `group::plan` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -17158,6 +20222,8 @@ Missing description Group: `group::plan` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -17170,6 +20236,8 @@ Missing description Group: `group::plan` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -17182,6 +20250,8 @@ Missing description Group: `group::plan` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -17194,6 +20264,8 @@ Missing description Group: `group::plan` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -17206,6 +20278,8 @@ Count of users todos created Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17218,6 +20292,8 @@ Unique users triggering deployments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -17230,6 +20306,8 @@ Total failed deployments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -17242,6 +20320,8 @@ Count creator_id from projects with repository mirroring enabled. Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -17254,6 +20334,8 @@ Unique users creating release tags Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -17266,6 +20348,8 @@ Total successful deployments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -17278,10 +20362,26 @@ Counts API fuzzing jobs Group: `group::fuzz testing` +Data Category: `Operational` + Status: `data_available` Tiers: +### `usage_activity_by_stage.secure.cluster_image_scanning_scans` + +Counts cluster image scanning jobs + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210618124854_cluster_image_scanning_scans.yml) + +Group: `group::container security` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `ultimate` + ### `usage_activity_by_stage.secure.container_scanning_scans` Counts container scanning jobs @@ -17290,6 +20390,8 @@ Counts container scanning jobs Group: `group::container security` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -17302,6 +20404,8 @@ Counts fuzzing jobs Group: `group::fuzz testing` +Data Category: `Operational` + Status: `data_available` Tiers: @@ -17312,11 +20416,13 @@ Counts dast jobs [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216182122_dast_scans.yml) -Group: `group::static analysis` +Group: `group::dynamic analysis` + +Data Category: `Operational` Status: `data_available` -Tiers: +Tiers: `ultimate` ### `usage_activity_by_stage.secure.dependency_scanning_scans` @@ -17326,6 +20432,8 @@ Total number of users running Dependency Scanning Scans Group: `group::composition analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -17338,21 +20446,25 @@ Counts sast jobs Group: `group::static analysis` +Data Category: `Operational` + Status: `data_available` -Tiers: +Tiers: `ultimate` ### `usage_activity_by_stage.secure.secret_detection_scans` -Counts secret detection jobs +counts secret detection jobs [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210216182123_secret_detection_scans.yml) Group: `group::static analysis` +Data Category: `Operational` + Status: `data_available` -Tiers: +Tiers: `ultimate` ### `usage_activity_by_stage.secure.user_api_fuzzing_dnd_jobs` @@ -17362,6 +20474,8 @@ Count of API Fuzzing `docker-in-docker` jobs by job name Group: `group::fuzz testing` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -17374,10 +20488,26 @@ Count of API Fuzzing jobs by job name Group: `group::fuzz testing` +Data Category: `Operational` + Status: `data_available` Tiers: `free` +### `usage_activity_by_stage.secure.user_api_fuzzing_scans` + +Number of users who have run a API Fuzzing scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210607044126_user_api_fuzzing_scans.yml) + +Group: `category::fuzz testing` + +Data Category: `Optional` + +Status: `data_available` + +Tiers: `ultimate` + ### `usage_activity_by_stage.secure.user_container_scanning_jobs` Distinct count per user of Container Scanning jobs run @@ -17386,6 +20516,22 @@ Distinct count per user of Container Scanning jobs run Group: `group::container security` +Data Category: `Operational` + +Status: `data_available` + +Tiers: `ultimate` + +### `usage_activity_by_stage.secure.user_container_scanning_scans` + +Number of users who have run a Container Scanning scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210607043902_user_container_scanning_scans.yml) + +Group: `group::composition analysis` + +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -17398,10 +20544,26 @@ Missing description Group: `` +Data Category: `Operational` + Status: `data_available` Tiers: `free` +### `usage_activity_by_stage.secure.user_coverage_fuzzing_scans` + +Number of users who have run a Coverage Fuzzing scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210607044040_user_coverage_fuzzing_scans.yml) + +Group: `category::fuzz testing` + +Data Category: `Optional` + +Status: `data_available` + +Tiers: `ultimate` + ### `usage_activity_by_stage.secure.user_dast_jobs` Count of DAST jobs @@ -17410,10 +20572,26 @@ Count of DAST jobs Group: `group::dynamic analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free` +### `usage_activity_by_stage.secure.user_dast_scans` + +Number of users who have run a DAST scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210607043109_user_dast_scans.yml) + +Group: `group::dynamic analysis` + +Data Category: `Optional` + +Status: `data_available` + +Tiers: `ultimate` + ### `usage_activity_by_stage.secure.user_dependency_scanning_jobs` Total number of users running Dependency Scanning jobs @@ -17422,6 +20600,22 @@ Total number of users running Dependency Scanning jobs Group: `group::composition analysis` +Data Category: `Operational` + +Status: `data_available` + +Tiers: `ultimate` + +### `usage_activity_by_stage.secure.user_dependency_scanning_scans` + +Number of users who have run a Dependency Scanning scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210607043819_user_dependency_scanning_scans.yml) + +Group: `group::composition analysis` + +Data Category: `Optional` + Status: `data_available` Tiers: `ultimate` @@ -17434,6 +20628,8 @@ Total number of users running License Scanning jobs Group: `group::composition analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -17446,34 +20642,68 @@ Users who set personal preference to see Details on Group information page Group: `group::threat insights` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` ### `usage_activity_by_stage.secure.user_sast_jobs` -Count of SAST jobs +Count of SAST jobs per user [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216182116_user_sast_jobs.yml) Group: `group::static analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` +### `usage_activity_by_stage.secure.user_sast_scans` + +Number of users who have run a SAST scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210607043741_user_sast_scans.yml) + +Group: `group::static analysis` + +Data Category: `Optional` + +Status: `data_available` + +Tiers: `ultimate` + ### `usage_activity_by_stage.secure.user_secret_detection_jobs` -Count of Secret Detection Jobs +Count of Secret Detection Jobs per user [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_all/20210216182118_user_secret_detection_jobs.yml) Group: `group::static analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` +### `usage_activity_by_stage.secure.user_secret_detection_scans` + +Number of users who have run a Secret Detection scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_all/20210607043957_user_secret_detection_scans.yml) + +Group: `group::static analysis` + +Data Category: `Optional` + +Status: `data_available` + +Tiers: `ultimate` + ### `usage_activity_by_stage.secure.user_unique_users_all_secure_scanners` Missing description @@ -17482,6 +20712,8 @@ Missing description Group: `group::secure` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -17494,6 +20726,8 @@ Unique count of builds in project Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17506,6 +20740,8 @@ Total pipelines in external repositories Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17518,6 +20754,8 @@ Total pipelines in GitLab repositories Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17530,6 +20768,8 @@ Total pipelines from an Auto DevOps template Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17542,6 +20782,8 @@ Total Pipelines from templates in repository Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17554,6 +20796,8 @@ Pipeline schedules in GitLab Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17566,6 +20810,8 @@ Distinct Users triggering Total pipelines Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17578,6 +20824,8 @@ Total configured Triggers in project Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17590,6 +20838,8 @@ Count of users creating managed clusters with Runner enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17602,6 +20852,8 @@ Projects with a GitHub service pipeline enabled Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -17614,6 +20866,8 @@ Total GitLab Managed clusters with Cert Manager enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17626,6 +20880,8 @@ Total GitLab Managed clusters with Helm enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17638,6 +20894,8 @@ Total GitLab Managed clusters with Ingress enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17650,6 +20908,8 @@ Total GitLab Managed clusters with Knative enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17662,6 +20922,8 @@ Total GitLab Managed disabled clusters Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17674,6 +20936,8 @@ Total GitLab Managed clusters currently enabled Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17686,6 +20950,8 @@ Number of Kubernetes clusters with clusters management project being set Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17698,6 +20964,8 @@ Total GitLab Managed clusters provisioned with GitLab on AWS EKS Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17710,6 +20978,8 @@ Total GitLab Managed clusters provisioned with GitLab on GCE GKE Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17722,6 +20992,8 @@ Total GitLab Managed clusters that are user provisioned Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17734,6 +21006,8 @@ Total GitLab Managed disabled clusters attached to groups Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17746,6 +21020,8 @@ Total GitLab Managed enabled clusters attached to groups Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17758,6 +21034,8 @@ Total GitLab Managed disabled clusters attached to the instance Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17770,6 +21048,8 @@ Total GitLab Managed enabled clusters attached to the instance Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17782,6 +21062,8 @@ Total GitLab Managed disabled clusters attached to projects Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17794,6 +21076,8 @@ Total GitLab Managed enabled clusters attached to projects Group: `group::configure` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17806,6 +21090,8 @@ Unique projects created in the past 28 days that have Slack notifications enable Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17818,6 +21104,8 @@ Unique projects created in the past 28 days that have Slack ‘/’ commands ena Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17830,6 +21118,8 @@ Projects with Prometheus alerting enabled Group: `group::monitor` +Data Category: `Optional` + Status: `removed` Tiers: `free`, `premium`, `ultimate` @@ -17842,6 +21132,8 @@ Monthly active users for design management Group: `group::product planning` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17854,6 +21146,8 @@ Aggregated value for wiki, design, and project repo Git write actions Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17866,6 +21160,8 @@ Number of unique users per month who edited a file from any web editor Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17878,6 +21174,8 @@ Count of monthly active users who have performed any Git operation (read/write/p Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17890,6 +21188,8 @@ Number of users using single file editor Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17902,6 +21202,8 @@ Number of users using the snippet editor Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17914,6 +21216,8 @@ Number of users using the static site editor Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17926,6 +21230,8 @@ Number of users editing using web IDE Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17938,6 +21244,8 @@ Unique monthly active users of the Wiki Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -17950,6 +21258,8 @@ Total number of project approval rules Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -17962,6 +21272,8 @@ Number of approval rules with the exact number of required approvers. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -17974,6 +21286,8 @@ Number of approval rules with fewer approvers than required. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -17986,6 +21300,8 @@ Number of approval rules with more approvers than required. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -17998,6 +21314,8 @@ Number of project approval rules scoped to a specific repo branch. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18010,6 +21328,8 @@ Count of users creating deploy keys in last 28 days. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18022,6 +21342,8 @@ Count of users creating regular keys in last 28 days. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18034,6 +21356,8 @@ Count of the number of users creating merge requests Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18046,6 +21370,8 @@ Monthly count of the number of merge request users Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18058,6 +21384,8 @@ Merge requests with added rules Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18070,6 +21398,8 @@ Count of merge requests with optional codeowner approval rules Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18082,6 +21412,8 @@ Number of merge requests which have overriden rules created at the project level Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18094,6 +21426,8 @@ Count of merge requests with required codeowner approval rules Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18106,6 +21440,8 @@ Count of total projects that require approval by code owners for code changes Group: `group::source code` +Data Category: `Operational` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18118,6 +21454,8 @@ Missing description Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -18130,6 +21468,8 @@ Count of the number of projects with setting to disable overriding approvers per Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18142,6 +21482,8 @@ Count of users creating projects that have a matching Git repository, result of Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18154,6 +21496,8 @@ Count of projects using code owners with code owners section feature Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18166,6 +21510,8 @@ Count of the number of projects without setting to disable overriding approvers Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18178,6 +21524,8 @@ Count of users creating projects with repositories making use of at least one pr Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18190,6 +21538,8 @@ Count of users creating projects with remote mirrors. Includes both push and pul Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18202,6 +21552,8 @@ Count of distinct author_id from snippets for last 28 days Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18214,6 +21566,8 @@ Count of unique users per month who create suggestions in merge request comments Group: `group::code review` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18226,6 +21580,8 @@ The total number of files which have been locked via the GitLab UI Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18238,6 +21594,8 @@ Number of paths/directories manually locked through the UI Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18250,6 +21608,8 @@ Number of unique users who have locked files or directories using LFS via the co Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18262,6 +21622,8 @@ Number of users creating path_locks in last 28 days. Group: `group::source code` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18274,6 +21636,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18286,6 +21650,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18298,10 +21664,26 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` +### `usage_activity_by_stage_monthly.manage.compliance_frameworks_with_pipeline` + +Count of compliance frameworks that have a pipeline configuration + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210622091519_compliance_frameworks_with_pipeline.yml) + +Group: `compliance` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `ultimate` + ### `usage_activity_by_stage_monthly.manage.custom_compliance_frameworks` Monthly count of all custom compliance framework labels @@ -18310,6 +21692,8 @@ Monthly count of all custom compliance framework labels Group: `compliance` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18322,6 +21706,8 @@ Missing description Group: `group::manage` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -18334,6 +21720,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -18346,6 +21734,8 @@ Number of group import states Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18358,6 +21748,8 @@ Whether group SAML is enabled Group: `group:access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18370,6 +21762,8 @@ Number of users who are group members for last 28 days Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18382,6 +21776,8 @@ Missing description Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18394,6 +21790,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -18406,6 +21804,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -18418,6 +21818,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -18430,6 +21832,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -18442,6 +21846,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18454,6 +21860,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18466,6 +21874,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18478,6 +21888,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18490,6 +21902,8 @@ Whether LDAP admin sync is enabled Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18502,6 +21916,8 @@ Has the instance configured [LDAP Group Sync](https://docs.gitlab.com/ee/adminis Group: `group::acess` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18514,6 +21930,8 @@ Number of users creating keys synced as part of LDAP for last 28 days. Group: `group::acess` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18526,6 +21944,8 @@ Number of LDAP servers configured Group: `group::manage` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18538,6 +21958,8 @@ Number of users that are linked to LDAP Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -18550,6 +21972,8 @@ Number of unique user logins using an OmniAuth provider Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18562,6 +21986,8 @@ Count of projects imported from Bitbucket Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18574,6 +22000,8 @@ Count of projects imported from Bitbucket Server Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18586,6 +22014,8 @@ Count of projects imported from Git Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18598,6 +22028,8 @@ Count of projects imported from Gitea Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18610,6 +22042,8 @@ Count of projects imported from GitHub Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18622,6 +22056,8 @@ Count of projects imported from GitLab using Project Export/Import Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18634,6 +22070,8 @@ Missing description Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18646,6 +22084,8 @@ Missing description Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18658,6 +22098,8 @@ Missing description Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18670,6 +22112,8 @@ Total count of projects imported Group: `group::import` +Data Category: `Optional` + Status: `implemented` Tiers: `free`, `premium`, `ultimate` @@ -18682,6 +22126,8 @@ Count of projects imported from Bitbucket Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -18694,6 +22140,8 @@ Count of projects imported from Bitbucket Server Group: `group::import` +Data Category: `Optional` + Status: `deprecated` Tiers: `free`, `premium`, `ultimate` @@ -18706,6 +22154,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18718,6 +22168,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18730,6 +22182,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18742,6 +22196,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18754,6 +22210,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18766,6 +22224,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18778,6 +22238,8 @@ Missing description Group: `` +Data Category: `Optional` + Status: `deprecated` Tiers: `free` @@ -18790,6 +22252,8 @@ Missing description Group: `group::manage` +Data Category: `Optional` + Status: `data_available` Tiers: @@ -18802,6 +22266,8 @@ Number of users from projects imported Group: `group::import` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18814,6 +22280,8 @@ Number of unique user logins using Google OAuth authentication Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18826,6 +22294,8 @@ Number of unique user logins using password authentication Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18838,6 +22308,8 @@ Number of unique user logins using two factor authentication Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18850,6 +22322,8 @@ Number of unique user logins using two factor via a U2F device Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18862,6 +22336,8 @@ Number of unique user logins using two factor via a WebAuthn device Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18874,6 +22350,8 @@ Number of users created in the month Group: `group::access` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18886,9 +22364,11 @@ Missing description Group: `group::manage` +Data Category: `Optional` + Status: `data_available` -Tiers: +Tiers: `premium`, `ultimate` ### `usage_activity_by_stage_monthly.monitor.clusters` @@ -18898,6 +22378,8 @@ Count users creating clusters in last 28 days. Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18910,6 +22392,8 @@ Users creating clusters with Prometheus enabled in last 28 days. Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18922,6 +22406,8 @@ Active users with enabled operations dashboard Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18934,6 +22420,8 @@ Active users with projects on operations dashboard Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18946,7 +22434,9 @@ Count of projects with Incident SLA enabled Group: `group::monitor` -Status: `data_available` +Data Category: `Optional` + +Status: `deprecated` Tiers: `premium`, `ultimate` @@ -18956,11 +22446,13 @@ Count of unique projects with an incident from an alert created in the last mont [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180526_projects_with_alert_incidents.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `usage_activity_by_stage_monthly.monitor.projects_with_error_tracking_enabled` @@ -18970,6 +22462,8 @@ Count of users creating projects with error tracking enabled. Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -18980,11 +22474,13 @@ Count of unique projects with an incident created in the last month [YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216180524_projects_with_incidents.yml) -Group: `group::health` +Group: `group::monitor` + +Data Category: `Optional` Status: `data_available` -Tiers: `free` +Tiers: `free`, `premium`, `ultimate` ### `usage_activity_by_stage_monthly.monitor.projects_with_tracing_enabled` @@ -18994,6 +22490,8 @@ Projects with tracing enabled Group: `group::monitor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19006,6 +22504,8 @@ The total number of projects in a given month with at least one package Group: `group::package` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19018,6 +22518,8 @@ Count of MAU creating assignee lists on Boards Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -19030,6 +22532,8 @@ Missing description Group: `group::plan` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -19042,6 +22546,8 @@ Count of users creating Issues in last 28 days. Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19054,6 +22560,8 @@ Count of MAU creating label lists on Boards Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19066,6 +22574,8 @@ Count of MAU created milestone lists on Boards Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -19078,6 +22588,8 @@ Count of MAU commenting on an issuable Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19090,6 +22602,8 @@ Count of MAU creating projects Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19102,6 +22616,8 @@ Missing description Group: `group::plan` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19114,6 +22630,8 @@ Missing description Group: `group::plan` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19126,6 +22644,8 @@ Missing description Group: `group::plan` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19138,6 +22658,8 @@ Missing description Group: `group::plan` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -19150,6 +22672,8 @@ Missing description Group: `group::plan` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19162,6 +22686,8 @@ Count of MAU creating todos Group: `group::project management` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19174,6 +22700,8 @@ Unique users triggering deployments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -19186,6 +22714,8 @@ Total failed deployments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -19198,6 +22728,8 @@ Count creator_id from projects with repository mirroring enabled. Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -19210,6 +22742,8 @@ Unique users creating release tags Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -19222,6 +22756,8 @@ Total successful deployments Group: `group::release` +Data Category: `Optional` + Status: `data_available` Tiers: `free` @@ -19234,6 +22770,8 @@ Counts of Pipelines that have at least 1 API Fuzzing Testing job Group: `group::fuzz testing` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -19246,10 +22784,40 @@ Missing description Group: `` +Data Category: `Operational` + Status: `data_available` Tiers: `free` +### `usage_activity_by_stage_monthly.secure.cluster_image_scanning_pipeline` + +Pipelines containing a Cluster Image Scanning job + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210618125224_cluster_image_scanning_pipeline.yml) + +Group: `group::container security` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `ultimate` + +### `usage_activity_by_stage_monthly.secure.cluster_image_scanning_scans` + +Counts cluster image scanning jobs + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210618101233_cluster_image_scanning_scans.yml) + +Group: `group::container security` + +Data Category: `Optional` + +Status: `implemented` + +Tiers: `ultimate` + ### `usage_activity_by_stage_monthly.secure.container_scanning_pipeline` Pipelines containing a Container Scanning job @@ -19258,6 +22826,8 @@ Pipelines containing a Container Scanning job Group: `group::container security` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -19270,6 +22840,8 @@ Missing description Group: `` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19282,6 +22854,8 @@ Counts of Pipelines that have at least 1 coverage-guided Fuzz Testing job Group: `group::fuzz testing` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -19294,6 +22868,8 @@ Missing description Group: `` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19306,6 +22882,8 @@ Count of pipelines that have at least 1 DAST job Group: `group::dynamic analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -19318,6 +22896,8 @@ Missing description Group: `` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19330,6 +22910,8 @@ Count of pipelines with successful Dependency Scanning jobs Group: `group::composition analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -19342,6 +22924,8 @@ Monthly number of users running Dependency Scanning Scans Group: `group::composition analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -19354,6 +22938,8 @@ Counts of Pipelines that have at least 1 SAST job Group: `group::static analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19366,6 +22952,8 @@ Missing description Group: `` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19378,6 +22966,8 @@ Counts of Pipelines that have at least 1 Secret Detection job Group: `group::static analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19390,6 +22980,8 @@ Missing description Group: `` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19402,6 +22994,8 @@ Count of API Fuzzing `docker-in-docker` jobs by job names Group: `group::fuzz testing` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19414,10 +23008,26 @@ Count of API Fuzzing jobs by job name Group: `group::fuzz testing` +Data Category: `Operational` + Status: `data_available` Tiers: `free` +### `usage_activity_by_stage_monthly.secure.user_api_fuzzing_scans` + +Number of users who have run a API Fuzzing scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210607043622_user_api_fuzzing_scans.yml) + +Group: `category::fuzz testing` + +Data Category: `Operational` + +Status: `data_available` + +Tiers: `ultimate` + ### `usage_activity_by_stage_monthly.secure.user_container_scanning_jobs` Distinct count per user of Container Scanning jobs run monthly @@ -19426,6 +23036,22 @@ Distinct count per user of Container Scanning jobs run monthly Group: `group::container security` +Data Category: `Operational` + +Status: `data_available` + +Tiers: `ultimate` + +### `usage_activity_by_stage_monthly.secure.user_container_scanning_scans` + +Number of users who have run a Container Scanning scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210607043336_user_container_scanning_scans.yml) + +Group: `group::composition analysis` + +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -19438,10 +23064,26 @@ Missing description Group: `` +Data Category: `Operational` + Status: `data_available` Tiers: `free` +### `usage_activity_by_stage_monthly.secure.user_coverage_fuzzing_scans` + +Number of users who have run a Coverage Fuzzing scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210607043509_user_coverage_fuzzing_scans.yml) + +Group: `category::fuzz testing` + +Data Category: `Operational` + +Status: `data_available` + +Tiers: `ultimate` + ### `usage_activity_by_stage_monthly.secure.user_dast_jobs` Users who run a DAST job @@ -19450,10 +23092,26 @@ Users who run a DAST job Group: `group::dynamic analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free` +### `usage_activity_by_stage_monthly.secure.user_dast_scans` + +Number of users who have run a DAST scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210607041718_user_dast_scans.yml) + +Group: `group::dynamic analysis` + +Data Category: `Operational` + +Status: `data_available` + +Tiers: `ultimate` + ### `usage_activity_by_stage_monthly.secure.user_dependency_scanning_jobs` Monthly number of users creating Dependency Scanning jobs @@ -19462,6 +23120,22 @@ Monthly number of users creating Dependency Scanning jobs Group: `group::composition analysis` +Data Category: `Operational` + +Status: `data_available` + +Tiers: `ultimate` + +### `usage_activity_by_stage_monthly.secure.user_dependency_scanning_scans` + +Number of users who have run a Dependency Scanning scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210607043301_user_dependency_scanning_scans.yml) + +Group: `group::composition analysis` + +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -19474,6 +23148,8 @@ Monthly number of users running License Scanning jobs Group: `group::composition analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -19486,6 +23162,8 @@ Users who set personal preference to see Security Dashboard on Group information Group: `group::threat insights` +Data Category: `Operational` + Status: `data_available` Tiers: `ultimate` @@ -19498,10 +23176,26 @@ Users who run a SAST job Group: `group::static analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` +### `usage_activity_by_stage_monthly.secure.user_sast_scans` + +Number of users who have run a SAST scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210607043218_user_sast_scans.yml) + +Group: `group::static analysis` + +Data Category: `Operational` + +Status: `data_available` + +Tiers: `ultimate` + ### `usage_activity_by_stage_monthly.secure.user_secret_detection_jobs` Users who run a Secret Detection job @@ -19510,10 +23204,26 @@ Users who run a Secret Detection job Group: `group::static analysis` +Data Category: `Operational` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` +### `usage_activity_by_stage_monthly.secure.user_secret_detection_scans` + +Number of users who have run a Secret Detection scan + +[YAML definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/counts_28d/20210607043410_user_secret_detection_scans.yml) + +Group: `group::static analysis` + +Data Category: `Operational` + +Status: `data_available` + +Tiers: `ultimate` + ### `usage_activity_by_stage_monthly.secure.user_unique_users_all_secure_scanners` Missing description @@ -19522,6 +23232,8 @@ Missing description Group: `group::secure` +Data Category: `Operational` + Status: `data_available` Tiers: `free` @@ -19534,6 +23246,8 @@ Unique monthly builds in project Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19546,6 +23260,8 @@ Total pipelines in external repositories in a month Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19558,6 +23274,8 @@ Total pipelines in GitLab repositories in a month Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19570,6 +23288,8 @@ Total pipelines from an Auto DevOps template Group: `group::configure` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19582,6 +23302,8 @@ Total Monthly Pipelines from templates in repository Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19594,6 +23316,8 @@ Total monthly Pipeline schedules in GitLab Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19606,6 +23330,8 @@ Distinct users triggering pipelines in a month Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate`, `free` @@ -19618,6 +23344,8 @@ Total configured Triggers in project Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19630,6 +23358,8 @@ Total GitLab Managed clusters with Runner enabled Group: `group::runner` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19642,6 +23372,8 @@ Projects with a GitHub repository mirror pipeline enabled Group: `group::pipeline execution` +Data Category: `Optional` + Status: `data_available` Tiers: `premium`, `ultimate` @@ -19654,6 +23386,8 @@ GitLab instance unique identifier Group: `group::product intelligence` +Data Category: `Standard` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19666,6 +23400,8 @@ Version of GitLab instance Group: `group::distribution` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` @@ -19678,6 +23414,8 @@ Whether Web IDE clientside preview is enabled Group: `group::editor` +Data Category: `Optional` + Status: `data_available` Tiers: `free`, `premium`, `ultimate` diff --git a/doc/development/usage_ping/index.md b/doc/development/usage_ping/index.md index de6a234e20c..aa06cb36f0c 100644 --- a/doc/development/usage_ping/index.md +++ b/doc/development/usage_ping/index.md @@ -1,1579 +1,9 @@ --- -stage: Growth -group: Product Intelligence -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments +redirect_to: '../service_ping/index.md' +remove_date: '2021-10-09' --- -# Usage Ping Guide +This file was moved to [another location](../service_ping/index.md). -> Introduced in GitLab Ultimate 11.2, more statistics. - -This guide describes Usage Ping's purpose and how it's implemented. - -For more information about Product Intelligence, see: - -- [Product Intelligence Guide](https://about.gitlab.com/handbook/product/product-intelligence-guide/) -- [Snowplow Guide](../snowplow/index.md) - -More links: - -- [Product Intelligence Direction](https://about.gitlab.com/direction/product-intelligence/) -- [Data Analysis Process](https://about.gitlab.com/handbook/business-ops/data-team/#data-analysis-process/) -- [Data for Product Managers](https://about.gitlab.com/handbook/business-ops/data-team/programs/data-for-product-managers/) -- [Data Infrastructure](https://about.gitlab.com/handbook/business-ops/data-team/platform/infrastructure/) - -## What is Usage Ping? - -Usage Ping is a process in GitLab that collects and sends a weekly payload to GitLab Inc. -The payload provides important high-level data that helps our product, support, -and sales teams understand how GitLab is used. For example, the data helps to: - -- Compare counts month over month (or week over week) to get a rough sense for how an instance uses - different product features. -- Collect other facts that help us classify and understand GitLab installations. -- Calculate our Stage Monthly Active Users (SMAU), which helps to measure the success of our stages - and features. - -Usage Ping information is not anonymous. It's linked to the instance's hostname. However, it does -not contain project names, usernames, or any other specific data. - -Sending a Usage Ping payload is optional and can be [disabled](#disable-usage-ping) on any instance. -When Usage Ping is enabled, GitLab gathers data from the other instances -and can show your instance's usage statistics to your users. - -### Terminology - -We use the following terminology to describe the Usage Ping components: - -- **Usage Ping**: the process that collects and generates a JSON payload. -- **Usage data**: the contents of the Usage Ping JSON payload. This includes metrics. -- **Metrics**: primarily made up of row counts for different tables in an instance's database. Each - metric has a corresponding [metric definition](metrics_dictionary.md#metrics-definition-and-validation) - in a YAML file. - -### Why should we enable Usage Ping? - -- The main purpose of Usage Ping is to build a better GitLab. Data about how GitLab is used is collected to better understand feature/stage adoption and usage, which helps us understand how GitLab is adding value and helps our team better understand the reasons why people use GitLab and with this knowledge we're able to make better product decisions. -- As a benefit of having the usage ping active, GitLab lets you analyze the users' activities over time of your GitLab installation. -- As a benefit of having the usage ping active, GitLab provides you with The DevOps Report,which gives you an overview of your entire instance's adoption of Concurrent DevOps from planning to monitoring. -- You get better, more proactive support. (assuming that our TAMs and support organization used the data to deliver more value) -- You get insight and advice into how to get the most value out of your investment in GitLab. Wouldn't you want to know that a number of features or values are not being adopted in your organization? -- You get a report that illustrates how you compare against other similar organizations (anonymized), with specific advice and recommendations on how to improve your DevOps processes. -- Usage Ping is enabled by default. To disable it, see [Disable Usage Ping](#disable-usage-ping). - -### Limitations - -- Usage Ping does not track frontend events things like page views, link clicks, or user sessions, and only focuses on aggregated backend events. -- Because of these limitations we recommend instrumenting your products with Snowplow for more detailed analytics on GitLab.com and use Usage Ping to track aggregated backend events on self-managed. - -## Usage Ping payload - -You can view the exact JSON payload sent to GitLab Inc. in the administration panel. To view the payload: - -1. Sign in as a user with [Administrator](../../user/permissions.md) permissions. -1. On the top bar, select **Menu >** **{admin}** **Admin**. -1. On the left sidebar, select **Settings > Metrics and profiling**. -1. Expand the **Usage statistics** section. -1. Select **Preview payload**. - -For an example payload, see [Example Usage Ping payload](#example-usage-ping-payload). - -## Disable Usage Ping - -To disable Usage Ping in the GitLab UI: - -1. Sign in as a user with [Administrator](../../user/permissions.md) permissions. -1. On the top bar, select **Menu >** **{admin}** **Admin**. -1. On the left sidebar, select **Settings > Metrics and profiling**. -1. Expand the **Usage statistics** section. -1. Clear the **Enable usage ping** checkbox and select **Save changes**. - -To disable Usage Ping and prevent it from being configured in the future through -the administration panel, Omnibus installs can set the following in -[`gitlab.rb`](https://docs.gitlab.com/omnibus/settings/configuration.html#configuration-options): - -```ruby -gitlab_rails['usage_ping_enabled'] = false -``` - -Source installations can set the following in `gitlab.yml`: - -```yaml -production: &base - # ... - gitlab: - # ... - usage_ping_enabled: false -``` - -## Usage Ping request flow - -The following example shows a basic request/response flow between a GitLab instance, the Versions Application, the License Application, Salesforce, the GitLab S3 Bucket, the GitLab Snowflake Data Warehouse, and Sisense: - -```mermaid -sequenceDiagram - participant GitLab Instance - participant Versions Application - participant Licenses Application - participant Salesforce - participant S3 Bucket - participant Snowflake DW - participant Sisense Dashboards - GitLab Instance->>Versions Application: Send Usage Ping - loop Process usage data - Versions Application->>Versions Application: Parse usage data - Versions Application->>Versions Application: Write to database - Versions Application->>Versions Application: Update license ping time - end - loop Process data for Salesforce - Versions Application-xLicenses Application: Request Zuora subscription id - Licenses Application-xVersions Application: Zuora subscription id - Versions Application-xSalesforce: Request Zuora account id by Zuora subscription id - Salesforce-xVersions Application: Zuora account id - Versions Application-xSalesforce: Usage data for the Zuora account - end - Versions Application->>S3 Bucket: Export Versions database - S3 Bucket->>Snowflake DW: Import data - Snowflake DW->>Snowflake DW: Transform data using dbt - Snowflake DW->>Sisense Dashboards: Data available for querying - Versions Application->>GitLab Instance: DevOps Report (Conversational Development Index) -``` - -## How Usage Ping works - -1. The Usage Ping [cron job](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/workers/gitlab_usage_ping_worker.rb#L30) is set in Sidekiq to run weekly. -1. When the cron job runs, it calls [`Gitlab::UsageData.to_json`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/services/submit_usage_ping_service.rb#L22). -1. `Gitlab::UsageData.to_json` [cascades down](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data.rb#L22) to ~400+ other counter method calls. -1. The response of all methods calls are [merged together](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data.rb#L14) into a single JSON payload in `Gitlab::UsageData.to_json`. -1. The JSON payload is then [posted to the Versions application]( https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/services/submit_usage_ping_service.rb#L20) - If a firewall exception is needed, the required URL depends on several things. If - the hostname is `version.gitlab.com`, the protocol is `TCP`, and the port number is `443`, - the required URL is <https://version.gitlab.com/>. - -## Usage Ping Metric Life cycle - -### 1. New metrics addition - -Please follow the [Implementing Usage Ping](#implementing-usage-ping) guide. - -### 2. Existing metric change - -Because we do not control when customers update their self-managed instances of GitLab, -we **STRONGLY DISCOURAGE** changes to the logic used to calculate any metric. -Any such changes lead to inconsistent reports from multiple GitLab instances. -If there is a problem with an existing metric, it's best to deprecate the existing metric, -and use it, side by side, with the desired new metric. - -Example: -Consider following change. Before GitLab 12.6, the `example_metric` was implemented as: - -```ruby -{ - ... - example_metric: distinct_count(Project, :creator_id) -} -``` - -For GitLab 12.6, the metric was changed to filter out archived projects: - -```ruby -{ - ... - example_metric: distinct_count(Project.non_archived, :creator_id) -} -``` - -In this scenario all instances running up to GitLab 12.5 continue to report `example_metric`, -including all archived projects, while all instances running GitLab 12.6 and higher filters -out such projects. As Usage Ping data is collected from all reporting instances, the -resulting dataset includes mixed data, which distorts any following business analysis. - -The correct approach is to add a new metric for GitLab 12.6 release with updated logic: - -```ruby -{ - ... - example_metric_without_archived: distinct_count(Project.non_archived, :creator_id) -} -``` - -and update existing business analysis artefacts to use `example_metric_without_archived` instead of `example_metric` - -### 3. Deprecate a metric - -If a metric is obsolete and you no longer use it, you can mark it as deprecated. - -For an example of the metric deprecation process take a look at this [example merge request](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/59899) - -To deprecate a metric: - -1. Check the following YAML files and verify the metric is not used in an aggregate: - - [`config/metrics/aggregates/*.yaml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/aggregates/) - - [`ee/config/metrics/aggregates/*.yaml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/aggregates/) - -1. Create an issue in the [GitLab Data Team - project](https://gitlab.com/gitlab-data/analytics/-/issues). Ask for - confirmation that the metric is not used by other teams, or in any of the SiSense - dashboards. - -1. Verify the metric is not used to calculate the conversational index. The - conversational index is a measure that reports back to self-managed instances - to inform administrators of the progress of DevOps adoption for the instance. - - You can check - [`CalculateConvIndexService`](https://gitlab.com/gitlab-services/version-gitlab-com/-/blob/master/app/services/calculate_conv_index_service.rb) - to view the metrics that are used. The metrics are represented - as the keys that are passed as a field argument into the `get_value` method. - -1. Document the deprecation in the metric's YAML definition. Set - the `status:` attribute to `deprecated`, for example: - - ```yaml - --- - key_path: analytics_unique_visits.analytics_unique_visits_for_any_target_monthly - description: Visits to any of the pages listed above per month - product_section: dev - product_stage: manage - product_group: group::analytics - product_category: - value_type: number - status: deprecated - time_frame: 28d - data_source: - distribution: - - ce - tier: - - free - ``` - -1. Replace the metric's instrumentation with a fixed value. This avoids wasting - resources to calculate the deprecated metric. In - [`lib/gitlab/usage_data.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data.rb) - or - [`ee/lib/ee/gitlab/usage_data.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/lib/ee/gitlab/usage_data.rb), - replace the code that calculates the metric's value with a fixed value that - indicates it's deprecated: - - ```ruby - module Gitlab - class UsageData - DEPRECATED_VALUE = -1000 - - def analytics_unique_visits_data - results['analytics_unique_visits_for_any_target'] = redis_usage_data { unique_visit_service.unique_visits_for(targets: :analytics) } - results['analytics_unique_visits_for_any_target_monthly'] = DEPRECATED_VALUE - - { analytics_unique_visits: results } - end - # ... - end - end - ``` - -1. Update the Metrics Dictionary following [guidelines instructions](dictionary.md). - -### 4. Remove a metric - -Only deprecated metrics can be removed from Usage Ping. - -For an example of the metric removal process take a look at this [example issue](https://gitlab.com/gitlab-org/gitlab/-/issues/297029) - -To remove a deprecated metric: - -1. Verify that removing the metric from the Usage Ping payload does not cause - errors in [Version App](https://gitlab.com/gitlab-services/version-gitlab-com) - when the updated payload is collected and processed. Version App collects - and persists all Usage Ping reports. To do that you can modify - [fixtures](https://gitlab.com/gitlab-services/version-gitlab-com/-/blob/master/spec/support/usage_data_helpers.rb#L540) - used to test - [`UsageDataController#create`](https://gitlab.com/gitlab-services/version-gitlab-com/-/blob/3760ef28/spec/controllers/usage_data_controller_spec.rb#L75) - endpoint, and assure that test suite does not fail when metric that you wish to remove is not included into test payload. - -1. Create an issue in the - [GitLab Data Team project](https://gitlab.com/gitlab-data/analytics/-/issues). - Ask for confirmation that the metric is not referred to in any SiSense dashboards and - can be safely removed from Usage Ping. Use this - [example issue](https://gitlab.com/gitlab-data/analytics/-/issues/7539) for guidance. - This step can be skipped if verification done during [deprecation process](#3-deprecate-a-metric) - reported that metric is not required by any data transformation in Snowflake data warehouse nor it is - used by any of SiSense dashboards. - -1. After you verify the metric can be safely removed, - update the attributes of the metric's YAML definition: - - - Set the `status:` to `removed`. - - Set `milestone_removed:` to the number of the - milestone in which the metric was removed. - - Do not remove the metric's YAML definition altogether. Some self-managed - instances might not immediately update to the latest version of GitLab, and - therefore continue to report the removed metric. The Product Intelligence team - requires a record of all removed metrics in order to identify and filter them. - - For example please take a look at this [merge request](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60149/diffs#b01f429a54843feb22265100c0e4fec1b7da1240_10_10). - -1. After you verify the metric can be safely removed, - remove the metric's instrumentation from - [`lib/gitlab/usage_data.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data.rb) - or - [`ee/lib/ee/gitlab/usage_data.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/lib/ee/gitlab/usage_data.rb). - - For example please take a look at this [merge request](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60149/diffs#6335dc533bd21df26db9de90a02dd66278c2390d_167_167). - -1. Remove any other records related to the metric: - - The feature flag YAML file at [`config/feature_flags/*/*.yaml`](https://gitlab.com/gitlab-org/gitlab/-/tree/master/config/feature_flags). - - The entry in the known events YAML file at [`lib/gitlab/usage_data_counters/known_events/*.yaml`](https://gitlab.com/gitlab-org/gitlab/-/tree/master/lib/gitlab/usage_data_counters/known_events). - -1. Update the Metrics Dictionary following [guidelines instructions](dictionary.md). - -## Implementing Usage Ping - -Usage Ping consists of two kinds of data, counters and observations. Counters track how often a certain event -happened over time, such as how many CI pipelines have run. They are monotonic and always trend up. -Observations are facts collected from one or more GitLab instances and can carry arbitrary data. There are no -general guidelines around how to collect those, due to the individual nature of that data. - -There are several types of counters which are all found in `usage_data.rb`: - -- **Ordinary Batch Counters:** Simple count of a given ActiveRecord_Relation -- **Distinct Batch Counters:** Distinct count of a given ActiveRecord_Relation in a given column -- **Sum Batch Counters:** Sum the values of a given ActiveRecord_Relation in a given column -- **Alternative Counters:** Used for settings and configurations -- **Redis Counters:** Used for in-memory counts. - -NOTE: -Only use the provided counter methods. Each counter method contains a built in fail safe to isolate each counter to avoid breaking the entire Usage Ping. - -### Why batch counting - -For large tables, PostgreSQL can take a long time to count rows due to MVCC [(Multi-version Concurrency Control)](https://en.wikipedia.org/wiki/Multiversion_concurrency_control). Batch counting is a counting method where a single large query is broken into multiple smaller queries. For example, instead of a single query querying 1,000,000 records, with batch counting, you can execute 100 queries of 10,000 records each. Batch counting is useful for avoiding database timeouts as each batch query is significantly shorter than one single long running query. - -For GitLab.com, there are extremely large tables with 15 second query timeouts, so we use batch counting to avoid encountering timeouts. Here are the sizes of some GitLab.com tables: - -| Table | Row counts in millions | -|------------------------------|------------------------| -| `merge_request_diff_commits` | 2280 | -| `ci_build_trace_sections` | 1764 | -| `merge_request_diff_files` | 1082 | -| `events` | 514 | - -The following operation methods are available for your use: - -- [Ordinary Batch Counters](#ordinary-batch-counters) -- [Distinct Batch Counters](#distinct-batch-counters) -- [Sum Batch Operation](#sum-batch-operation) -- [Add Operation](#add-operation) -- [Estimated Batch Counters](#estimated-batch-counters) - -Batch counting requires indexes on columns to calculate max, min, and range queries. In some cases, -you may need to add a specialized index on the columns involved in a counter. - -### Ordinary Batch Counters - -Handles `ActiveRecord::StatementInvalid` error - -Simple count of a given `ActiveRecord_Relation`, does a non-distinct batch count, smartly reduces `batch_size`, and handles errors. - -Method: `count(relation, column = nil, batch: true, start: nil, finish: nil)` - -Arguments: - -- `relation` the ActiveRecord_Relation to perform the count -- `column` the column to perform the count on, by default is the primary key -- `batch`: default `true` to use batch counting -- `start`: custom start of the batch counting to avoid complex min calculations -- `end`: custom end of the batch counting to avoid complex min calculations - -Examples: - -```ruby -count(User.active) -count(::Clusters::Cluster.aws_installed.enabled, :cluster_id) -count(::Clusters::Cluster.aws_installed.enabled, :cluster_id, start: ::Clusters::Cluster.minimum(:id), finish: ::Clusters::Cluster.maximum(:id)) -``` - -### Distinct Batch Counters - -Handles `ActiveRecord::StatementInvalid` error - -Distinct count of a given `ActiveRecord_Relation` on given column, a distinct batch count, smartly reduces `batch_size`, and handles errors. - -Method: `distinct_count(relation, column = nil, batch: true, batch_size: nil, start: nil, finish: nil)` - -Arguments: - -- `relation` the ActiveRecord_Relation to perform the count -- `column` the column to perform the distinct count, by default is the primary key -- `batch`: default `true` to use batch counting -- `batch_size`: if none set it uses default value 10000 from `Gitlab::Database::BatchCounter` -- `start`: custom start of the batch counting to avoid complex min calculations -- `end`: custom end of the batch counting to avoid complex min calculations - -WARNING: -Counting over non-unique columns can lead to performance issues. Take a look at the [iterating tables in batches](../iterating_tables_in_batches.md) guide for more details. - -Examples: - -```ruby -distinct_count(::Project, :creator_id) -distinct_count(::Note.with_suggestions.where(time_period), :author_id, start: ::User.minimum(:id), finish: ::User.maximum(:id)) -distinct_count(::Clusters::Applications::CertManager.where(time_period).available.joins(:cluster), 'clusters.user_id') -``` - -### Sum Batch Operation - -Handles `ActiveRecord::StatementInvalid` error - -Sum the values of a given ActiveRecord_Relation on given column and handles errors. - -Method: `sum(relation, column, batch_size: nil, start: nil, finish: nil)` - -Arguments: - -- `relation` the ActiveRecord_Relation to perform the operation -- `column` the column to sum on -- `batch_size`: if none set it uses default value 1000 from `Gitlab::Database::BatchCounter` -- `start`: custom start of the batch counting to avoid complex min calculations -- `end`: custom end of the batch counting to avoid complex min calculations - -Examples: - -```ruby -sum(JiraImportState.finished, :imported_issues_count) -``` - -### Grouping & Batch Operations - -The `count`, `distinct_count`, and `sum` batch counters can accept an `ActiveRecord::Relation` -object, which groups by a specified column. With a grouped relation, the methods do batch counting, -handle errors, and returns a hash table of key-value pairs. - -Examples: - -```ruby -count(Namespace.group(:type)) -# returns => {nil=>179, "Group"=>54} - -distinct_count(Project.group(:visibility_level), :creator_id) -# returns => {0=>1, 10=>1, 20=>11} - -sum(Issue.group(:state_id), :weight)) -# returns => {1=>3542, 2=>6820} -``` - -### Add Operation - -Handles `StandardError`. - -Returns `-1` if any of the arguments are `-1`. - -Sum the values given as parameters. - -Method: `add(*args)` - -Examples - -```ruby -project_imports = distinct_count(::Project.where.not(import_type: nil), :creator_id) -bulk_imports = distinct_count(::BulkImport, :user_id) - - add(project_imports, bulk_imports) -``` - -### Estimated Batch Counters - -> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/48233) in GitLab 13.7. - -Estimated batch counter functionality handles `ActiveRecord::StatementInvalid` errors -when used through the provided `estimate_batch_distinct_count` method. -Errors return a value of `-1`. - -WARNING: -This functionality estimates a distinct count of a specific ActiveRecord_Relation in a given column, -which uses the [HyperLogLog](http://algo.inria.fr/flajolet/Publications/FlFuGaMe07.pdf) algorithm. -As the HyperLogLog algorithm is probabilistic, the **results always include error**. -The highest encountered error rate is 4.9%. - -When correctly used, the `estimate_batch_distinct_count` method enables efficient counting over -columns that contain non-unique values, which can not be assured by other counters. - -#### estimate_batch_distinct_count method - -Method: `estimate_batch_distinct_count(relation, column = nil, batch_size: nil, start: nil, finish: nil)` - -The [method](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/utils/usage_data.rb#L63) -includes the following arguments: - -- `relation`: The ActiveRecord_Relation to perform the count. -- `column`: The column to perform the distinct count. The default is the primary key. -- `batch_size`: From `Gitlab::Database::PostgresHll::BatchDistinctCounter::DEFAULT_BATCH_SIZE`. Default value: 10,000. -- `start`: The custom start of the batch count, to avoid complex minimum calculations. -- `finish`: The custom end of the batch count to avoid complex maximum calculations. - -The method includes the following prerequisites: - -1. The supplied `relation` must include the primary key defined as the numeric column. - For example: `id bigint NOT NULL`. -1. The `estimate_batch_distinct_count` can handle a joined relation. To use its ability to - count non-unique columns, the joined relation **must NOT** have a one-to-many relationship, - such as `has_many :boards`. -1. Both `start` and `finish` arguments should always represent primary key relationship values, - even if the estimated count refers to another column, for example: - - ```ruby - estimate_batch_distinct_count(::Note, :author_id, start: ::Note.minimum(:id), finish: ::Note.maximum(:id)) - ``` - -Examples: - -1. Simple execution of estimated batch counter, with only relation provided, - returned value represents estimated number of unique values in `id` column - (which is the primary key) of `Project` relation: - - ```ruby - estimate_batch_distinct_count(::Project) - ``` - -1. Execution of estimated batch counter, where provided relation has applied - additional filter (`.where(time_period)`), number of unique values estimated - in custom column (`:author_id`), and parameters: `start` and `finish` together - apply boundaries that defines range of provided relation to analyze: - - ```ruby - estimate_batch_distinct_count(::Note.with_suggestions.where(time_period), :author_id, start: ::Note.minimum(:id), finish: ::Note.maximum(:id)) - ``` - -1. Execution of estimated batch counter with joined relation (`joins(:cluster)`), - for a custom column (`'clusters.user_id'`): - - ```ruby - estimate_batch_distinct_count(::Clusters::Applications::CertManager.where(time_period).available.joins(:cluster), 'clusters.user_id') - ``` - -When instrumenting metric with usage of estimated batch counter please add -`_estimated` suffix to its name, for example: - -```ruby - "counts": { - "ci_builds_estimated": estimate_batch_distinct_count(Ci::Build), - ... -``` - -### Redis Counters - -Handles `::Redis::CommandError` and `Gitlab::UsageDataCounters::BaseCounter::UnknownEvent` -returns -1 when a block is sent or hash with all values -1 when a `counter(Gitlab::UsageDataCounters)` is sent -different behavior due to 2 different implementations of Redis counter - -Method: `redis_usage_data(counter, &block)` - -Arguments: - -- `counter`: a counter from `Gitlab::UsageDataCounters`, that has `fallback_totals` method implemented -- or a `block`: which is evaluated - -#### Ordinary Redis Counters - -Examples of implementation: - -- Using Redis methods [`INCR`](https://redis.io/commands/incr), [`GET`](https://redis.io/commands/get), and [`Gitlab::UsageDataCounters::WikiPageCounter`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data_counters/wiki_page_counter.rb) -- Using Redis methods [`HINCRBY`](https://redis.io/commands/hincrby), [`HGETALL`](https://redis.io/commands/hgetall), and [`Gitlab::UsageCounters::PodLogs`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_counters/pod_logs.rb) - -##### UsageData API Tracking - -<!-- There's nearly identical content in `##### Adding new events`. If you fix errors here, you may need to fix the same errors in the other location. --> - -1. Track event using `UsageData` API - - Increment event count using ordinary Redis counter, for given event name. - - Tracking events using the `UsageData` API requires the `usage_data_api` feature flag to be enabled, which is enabled by default. - - API requests are protected by checking for a valid CSRF token. - - To be able to increment the values, the related feature `usage_data_<event_name>` should be enabled. - - ```plaintext - POST /usage_data/increment_counter - ``` - - | Attribute | Type | Required | Description | - | :-------- | :--- | :------- | :---------- | - | `event` | string | yes | The event name it should be tracked | - - Response - - - `200` if event was tracked - - `400 Bad request` if event parameter is missing - - `401 Unauthorized` if user is not authenticated - - `403 Forbidden` for invalid CSRF token provided - -1. Track events using JavaScript/Vue API helper which calls the API above - - Note that `usage_data_api` and `usage_data_#{event_name}` should be enabled to be able to track events - - ```javascript - import api from '~/api'; - - api.trackRedisCounterEvent('my_already_defined_event_name'), - ``` - -#### Redis HLL Counters - -WARNING: -HyperLogLog (HLL) is a probabilistic algorithm and its **results always includes some small error**. According to [Redis documentation](https://redis.io/commands/pfcount), data from -used HLL implementation is "approximated with a standard error of 0.81%". - -With `Gitlab::UsageDataCounters::HLLRedisCounter` we have available data structures used to count unique values. - -Implemented using Redis methods [PFADD](https://redis.io/commands/pfadd) and [PFCOUNT](https://redis.io/commands/pfcount). - -##### Adding new events - -1. Define events in [`known_events`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data_counters/known_events/). - - Example event: - - ```yaml - - name: users_creating_epics - category: epics_usage - redis_slot: users - aggregation: weekly - feature_flag: track_epics_activity - ``` - - Keys: - - - `name`: unique event name. - - Name format for Redis HLL events `<name>_<redis_slot>`. - - [See Metric name](metrics_dictionary.md#metric-name) for a complete guide on metric naming suggestion. - - Consider including in the event's name the Redis slot to be able to count totals for a specific category. - - Example names: `users_creating_epics`, `users_triggering_security_scans`. - - - `category`: event category. Used for getting total counts for events in a category, for easier - access to a group of events. - - `redis_slot`: optional Redis slot. Default value: event name. Only event data that is stored in the same slot - can be aggregated. Ensure keys are in the same slot. For example: - `users_creating_epics` with `redis_slot: 'users'` builds Redis key - `{users}_creating_epics-2020-34`. If `redis_slot` is not defined the Redis key will - be `{users_creating_epics}-2020-34`. - Recommended slots to use are: `users`, `projects`. This is the value we count. - - `expiry`: expiry time in days. Default: 29 days for daily aggregation and 6 weeks for weekly - aggregation. - - `aggregation`: may be set to a `:daily` or `:weekly` key. Defines how counting data is stored in Redis. - Aggregation on a `daily` basis does not pull more fine grained data. - - `feature_flag`: optional `default_enabled: :yaml`. If no feature flag is set then the tracking is enabled. One feature flag can be used for multiple events. For details, see our [GitLab internal Feature flags](../feature_flags/index.md) documentation. The feature flags are owned by the group adding the event tracking. - -Use one of the following methods to track events: - -1. Track event in controller using `RedisTracking` module with `track_redis_hll_event(*controller_actions, name:, if: nil, &block)`. - - Arguments: - - - `controller_actions`: controller actions we want to track. - - `name`: event name. - - `if`: optional custom conditions, using the same format as with Rails callbacks. - - `&block`: optional block that computes and returns the `custom_id` that we want to track. This will override the `visitor_id`. - - Example usage: - - ```ruby - # controller - class ProjectsController < Projects::ApplicationController - include RedisTracking - - skip_before_action :authenticate_user!, only: :show - track_redis_hll_event :index, :show, name: 'users_visiting_projects' - - def index - render html: 'index' - end - - def new - render html: 'new' - end - - def show - render html: 'show' - end - end - ``` - -1. Track event in API using `increment_unique_values(event_name, values)` helper method. - - Arguments: - - - `event_name`: event name. - - `values`: values counted, one value or array of values. - - Example usage: - - ```ruby - get ':id/registry/repositories' do - repositories = ContainerRepositoriesFinder.new( - user: current_user, subject: user_group - ).execute - - increment_unique_values('users_listing_repositories', current_user.id) - - present paginate(repositories), with: Entities::ContainerRegistry::Repository, tags: params[:tags], tags_count: params[:tags_count] - end - ``` - -1. Track event using `track_usage_event(event_name, values)` in services and GraphQL - - Increment unique values count using Redis HLL, for given event name. - - Example: - - [Track usage event for incident created in service](https://gitlab.com/gitlab-org/gitlab/-/blob/v13.8.3-ee/app/services/issues/update_service.rb#L66) - - [Track usage event for incident created in GraphQL](https://gitlab.com/gitlab-org/gitlab/-/blob/v13.8.3-ee/app/graphql/mutations/alert_management/update_alert_status.rb#L16) - - ```ruby - track_usage_event(:incident_management_incident_created, current_user.id) - ``` - -<!-- There's nearly identical content in `##### UsageData API Tracking`. If you find / fix errors here, you may need to fix errors in that section too. --> - -1. Track event using `UsageData` API - - Increment unique users count using Redis HLL, for given event name. - - Tracking events using the `UsageData` API requires the `usage_data_api` feature flag to be enabled, which is enabled by default. - - API requests are protected by checking for a valid CSRF token. - - ```plaintext - POST /usage_data/increment_unique_users - ``` - - | Attribute | Type | Required | Description | - | :-------- | :--- | :------- | :---------- | - | `event` | string | yes | The event name it should be tracked | - - Response - - Return 200 if tracking failed for any reason. - - - `200` if event was tracked or any errors - - `400 Bad request` if event parameter is missing - - `401 Unauthorized` if user is not authenticated - - `403 Forbidden` for invalid CSRF token provided - -1. Track events using JavaScript/Vue API helper which calls the API above - - Example usage for an existing event already defined in [known events](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data_counters/known_events/): - - Usage Data API is behind `usage_data_api` feature flag which, as of GitLab 13.7, is - now set to `default_enabled: true`. - - ```javascript - import api from '~/api'; - - api.trackRedisHllUserEvent('my_already_defined_event_name'), - ``` - -1. Get event data using `Gitlab::UsageDataCounters::HLLRedisCounter.unique_events(event_names:, start_date:, end_date:, context: '')`. - - Arguments: - - - `event_names`: the list of event names. - - `start_date`: start date of the period for which we want to get event data. - - `end_date`: end date of the period for which we want to get event data. - - `context`: context of the event. Allowed values are `default`, `free`, `bronze`, `silver`, `gold`, `starter`, `premium`, `ultimate`. - -1. Testing tracking and getting unique events - -Trigger events in rails console by using `track_event` method - - ```ruby - Gitlab::UsageDataCounters::HLLRedisCounter.track_event('users_viewing_compliance_audit_events', values: 1) - Gitlab::UsageDataCounters::HLLRedisCounter.track_event('users_viewing_compliance_audit_events', values: [2, 3]) - ``` - -Next, get the unique events for the current week. - - ```ruby - # Get unique events for metric for current_week - Gitlab::UsageDataCounters::HLLRedisCounter.unique_events(event_names: 'users_viewing_compliance_audit_events', - start_date: Date.current.beginning_of_week, end_date: Date.current.next_week) - ``` - -##### Recommendations - -We have the following recommendations for [Adding new events](#adding-new-events): - -- Event aggregation: weekly. -- Key expiry time: - - Daily: 29 days. - - Weekly: 42 days. -- When adding new metrics, use a [feature flag](../../operations/feature_flags.md) to control the impact. -- For feature flags triggered by another service, set `default_enabled: false`, - - Events can be triggered using the `UsageData` API, which helps when there are > 10 events per change - -##### Enable/Disable Redis HLL tracking - -Events are tracked behind optional [feature flags](../feature_flags/index.md) due to concerns for Redis performance and scalability. - -For a full list of events and corresponding feature flags see, [known_events](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data_counters/known_events/) files. - -To enable or disable tracking for specific event in <https://gitlab.com> or <https://about.staging.gitlab.com>, run commands such as the following to -[enable or disable the corresponding feature](../feature_flags/index.md). - -```shell -/chatops run feature set <feature_name> true -/chatops run feature set <feature_name> false -``` - -We can also disable tracking completely by using the global flag: - -```shell -/chatops run feature set redis_hll_tracking true -/chatops run feature set redis_hll_tracking false -``` - -##### Known events are added automatically in usage data payload - -All events added in [`known_events/common.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data_counters/known_events/common.yml) are automatically added to usage data generation under the `redis_hll_counters` key. This column is stored in [version-app as a JSON](https://gitlab.com/gitlab-services/version-gitlab-com/-/blob/master/db/schema.rb#L209). -For each event we add metrics for the weekly and monthly time frames, and totals for each where applicable: - -- `#{event_name}_weekly`: Data for 7 days for daily [aggregation](#adding-new-events) events and data for the last complete week for weekly [aggregation](#adding-new-events) events. -- `#{event_name}_monthly`: Data for 28 days for daily [aggregation](#adding-new-events) events and data for the last 4 complete weeks for weekly [aggregation](#adding-new-events) events. - -Redis HLL implementation calculates automatic total metrics, if there are more than one metric for the same category, aggregation, and Redis slot. - -- `#{category}_total_unique_counts_weekly`: Total unique counts for events in the same category for the last 7 days or the last complete week, if events are in the same Redis slot and we have more than one metric. -- `#{category}_total_unique_counts_monthly`: Total unique counts for events in same category for the last 28 days or the last 4 complete weeks, if events are in the same Redis slot and we have more than one metric. - -Example of `redis_hll_counters` data: - -```ruby -{:redis_hll_counters=> - {"compliance"=> - {"users_viewing_compliance_dashboard_weekly"=>0, - "users_viewing_compliance_dashboard_monthly"=>0, - "users_viewing_compliance_audit_events_weekly"=>0, - "users_viewing_audit_events_monthly"=>0, - "compliance_total_unique_counts_weekly"=>0, - "compliance_total_unique_counts_monthly"=>0}, - "analytics"=> - {"users_viewing_analytics_group_devops_adoption_weekly"=>0, - "users_viewing_analytics_group_devops_adoption_monthly"=>0, - "analytics_total_unique_counts_weekly"=>0, - "analytics_total_unique_counts_monthly"=>0}, - "ide_edit"=> - {"users_editing_by_web_ide_weekly"=>0, - "users_editing_by_web_ide_monthly"=>0, - "users_editing_by_sfe_weekly"=>0, - "users_editing_by_sfe_monthly"=>0, - "ide_edit_total_unique_counts_weekly"=>0, - "ide_edit_total_unique_counts_monthly"=>0} - } -``` - -Example usage: - -```ruby -# Redis Counters -redis_usage_data(Gitlab::UsageDataCounters::WikiPageCounter) -redis_usage_data { ::Gitlab::UsageCounters::PodLogs.usage_totals[:total] } - -# Define events in common.yml https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data_counters/known_events/common.yml - -# Tracking events -Gitlab::UsageDataCounters::HLLRedisCounter.track_event('users_expanding_vulnerabilities', values: visitor_id) - -# Get unique events for metric -redis_usage_data { Gitlab::UsageDataCounters::HLLRedisCounter.unique_events(event_names: 'users_expanding_vulnerabilities', start_date: 28.days.ago, end_date: Date.current) } -``` - -### Alternative Counters - -Handles `StandardError` and fallbacks into -1 this way not all measures fail if we encounter one exception. -Mainly used for settings and configurations. - -Method: `alt_usage_data(value = nil, fallback: -1, &block)` - -Arguments: - -- `value`: a simple static value in which case the value is simply returned. -- or a `block`: which is evaluated -- `fallback: -1`: the common value used for any metrics that are failing. - -Usage: - -```ruby -alt_usage_data { Gitlab::VERSION } -alt_usage_data { Gitlab::CurrentSettings.uuid } -alt_usage_data(999) -``` - -### Adding counters to build new metrics - -When adding the results of two counters, use the `add` usage data method that -handles fallback values and exceptions. It also generates a valid [SQL export](#exporting-usage-ping-sql-queries-and-definitions). - -Example usage: - -```ruby -add(User.active, User.bot) -``` - -### Prometheus Queries - -In those cases where operational metrics should be part of Usage Ping, a database or Redis query is unlikely -to provide useful data. Instead, Prometheus might be more appropriate, because most GitLab architectural -components publish metrics to it that can be queried back, aggregated, and included as usage data. - -NOTE: -Prometheus as a data source for Usage Ping is currently only available for single-node Omnibus installations -that are running the [bundled Prometheus](../../administration/monitoring/prometheus/index.md) instance. - -To query Prometheus for metrics, a helper method is available to `yield` a fully configured -`PrometheusClient`, given it is available as per the note above: - -```ruby -with_prometheus_client do |client| - response = client.query('<your query>') - ... -end -``` - -Please refer to [the `PrometheusClient` definition](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/prometheus_client.rb) -for how to use its API to query for data. - -### Fallback values for UsagePing - -We return fallback values in these cases: - -| Case | Value | -|-----------------------------|-------| -| Deprecated Metric | -1000 | -| Timeouts, general failures | -1 | -| Standard errors in counters | -2 | - -## Developing and testing Usage Ping - -### 1. Naming and placing the metrics - -Add the metric in one of the top level keys - -- `settings`: for settings related metrics. -- `counts_weekly`: for counters that have data for the most recent 7 days. -- `counts_monthly`: for counters that have data for the most recent 28 days. -- `counts`: for counters that have data for all time. - -### 2. Use your Rails console to manually test counters - -```ruby -# count -Gitlab::UsageData.count(User.active) -Gitlab::UsageData.count(::Clusters::Cluster.aws_installed.enabled, :cluster_id) - -# count distinct -Gitlab::UsageData.distinct_count(::Project, :creator_id) -Gitlab::UsageData.distinct_count(::Note.with_suggestions.where(time_period), :author_id, start: ::User.minimum(:id), finish: ::User.maximum(:id)) -``` - -### 3. Generate the SQL query - -Your Rails console returns the generated SQL queries. - -Example: - -```ruby -pry(main)> Gitlab::UsageData.count(User.active) - (2.6ms) SELECT "features"."key" FROM "features" - (15.3ms) SELECT MIN("users"."id") FROM "users" WHERE ("users"."state" IN ('active')) AND ("users"."user_type" IS NULL OR "users"."user_type" IN (6, 4)) - (2.4ms) SELECT MAX("users"."id") FROM "users" WHERE ("users"."state" IN ('active')) AND ("users"."user_type" IS NULL OR "users"."user_type" IN (6, 4)) - (1.9ms) SELECT COUNT("users"."id") FROM "users" WHERE ("users"."state" IN ('active')) AND ("users"."user_type" IS NULL OR "users"."user_type" IN (6, 4)) AND "users"."id" BETWEEN 1 AND 100000 -``` - -### 4. Optimize queries with #database-lab - -Paste the SQL query into `#database-lab` to see how the query performs at scale. - -- `#database-lab` is a Slack channel which uses a production-sized environment to test your queries. -- GitLab.com's production database has a 15 second timeout. -- Any single query must stay below [1 second execution time](../query_performance.md#timing-guidelines-for-queries) with cold caches. -- Add a specialized index on columns involved to reduce the execution time. - -To have an understanding of the query's execution we add in the MR description the following information: - -- For counters that have a `time_period` test we add information for both cases: - - `time_period = {}` for all time periods - - `time_period = { created_at: 28.days.ago..Time.current }` for last 28 days period -- Execution plan and query time before and after optimization -- Query generated for the index and time -- Migration output for up and down execution - -We also use `#database-lab` and [explain.depesz.com](https://explain.depesz.com/). For more details, see the [database review guide](../database_review.md#preparation-when-adding-or-modifying-queries). - -#### Optimization recommendations and examples - -- Use specialized indexes [example 1](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26871), [example 2](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26445). -- Use defined `start` and `finish`, and simple queries. These values can be memoized and reused, [example](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/37155). -- Avoid joins and write the queries as simply as possible, [example](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/36316). -- Set a custom `batch_size` for `distinct_count`, [example](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38000). - -### 5. Add the metric definition - -[Check Metrics Dictionary Guide](metrics_dictionary.md) - -When adding, updating, or removing metrics, please update the [Metrics Dictionary](dictionary.md). - -### 6. Add new metric to Versions Application - -Check if new metrics need to be added to the Versions Application. See `usage_data` [schema](https://gitlab.com/gitlab-services/version-gitlab-com/-/blob/master/db/schema.rb#L147) and usage data [parameters accepted](https://gitlab.com/gitlab-services/version-gitlab-com/-/blob/master/app/services/usage_ping.rb). Any metrics added under the `counts` key are saved in the `stats` column. - -### 7. Add the feature label - -Add the `feature` label to the Merge Request for new Usage Ping metrics. These are user-facing changes and are part of expanding the Usage Ping feature. - -### 8. Add a changelog - -Ensure you comply with the [Changelog entries guide](../changelog.md). - -### 9. Ask for a Product Intelligence Review - -On GitLab.com, we have DangerBot setup to monitor Product Intelligence related files and DangerBot recommends a [Product Intelligence review](product_intelligence_review.md). Mention `@gitlab-org/growth/product_intelligence/engineers` in your MR for a review. - -### 10. Verify your metric - -On GitLab.com, the Product Intelligence team regularly [monitors Usage Ping](https://gitlab.com/groups/gitlab-org/-/epics/6000). -They may alert you that your metrics need further optimization to run quicker and with greater success. - -The Usage Ping JSON payload for GitLab.com is shared in the -[#g_product_intelligence](https://gitlab.slack.com/archives/CL3A7GFPF) Slack channel every week. - -You may also use the [Usage Ping QA dashboard](https://app.periscopedata.com/app/gitlab/632033/Usage-Ping-QA) to check how well your metric performs. The dashboard allows filtering by GitLab version, by "Self-managed" & "SaaS" and shows you how many failures have occurred for each metric. Whenever you notice a high failure rate, you may re-optimize your metric. - -### Usage Ping local setup - -To set up Usage Ping locally, you must: - -1. [Set up local repositories](#set-up-local-repositories). -1. [Test local setup](#test-local-setup). -1. (Optional) [Test Prometheus-based usage ping](#test-prometheus-based-usage-ping). - -#### Set up local repositories - -1. Clone and start [GitLab](https://gitlab.com/gitlab-org/gitlab-development-kit). -1. Clone and start [Versions Application](https://gitlab.com/gitlab-services/version-gitlab-com). - Make sure to run `docker-compose up` to start a PostgreSQL and Redis instance. -1. Point GitLab to the Versions Application endpoint instead of the default endpoint: - 1. Open [submit_usage_ping_service.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/services/submit_usage_ping_service.rb#L4) in your local and modified `PRODUCTION_URL`. - 1. Set it to the local Versions Application URL `http://localhost:3000/usage_data`. - -#### Test local setup - -1. Using the `gitlab` Rails console, manually trigger a usage ping: - - ```ruby - SubmitUsagePingService.new.execute - ``` - -1. Use the `versions` Rails console to check the usage ping was successfully received, - parsed, and stored in the Versions database: - - ```ruby - UsageData.last - ``` - -### Test Prometheus-based usage ping - -If the data submitted includes metrics [queried from Prometheus](#prometheus-queries) -you want to inspect and verify, you must: - -- Ensure that a Prometheus server is running locally. -- Ensure the respective GitLab components are exporting metrics to the Prometheus server. - -If you do not need to test data coming from Prometheus, no further action -is necessary. Usage Ping should degrade gracefully in the absence of a running Prometheus server. - -Three kinds of components may export data to Prometheus, and are included in Usage Ping: - -- [`node_exporter`](https://github.com/prometheus/node_exporter): Exports node metrics - from the host machine. -- [`gitlab-exporter`](https://gitlab.com/gitlab-org/gitlab-exporter): Exports process metrics - from various GitLab components. -- Other various GitLab services, such as Sidekiq and the Rails server, which export their own metrics. - -#### Test with an Omnibus container - -This is the recommended approach to test Prometheus based Usage Ping. - -The easiest way to verify your changes is to build a new Omnibus image from your code branch by using CI, then download the image -and run a local container instance: - -1. From your merge request, click on the `qa` stage, then trigger the `package-and-qa` job. This job triggers an Omnibus -build in a [downstream pipeline of the `omnibus-gitlab-mirror` project](https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/-/pipelines). -1. In the downstream pipeline, wait for the `gitlab-docker` job to finish. -1. Open the job logs and locate the full container name including the version. It takes the following form: `registry.gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/gitlab-ee:<VERSION>`. -1. On your local machine, make sure you are signed in to the GitLab Docker registry. You can find the instructions for this in -[Authenticate to the GitLab Container Registry](../../user/packages/container_registry/index.md#authenticate-with-the-container-registry). -1. Once signed in, download the new image by using `docker pull registry.gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/gitlab-ee:<VERSION>` -1. For more information about working with and running Omnibus GitLab containers in Docker, please refer to [GitLab Docker images](https://docs.gitlab.com/omnibus/docker/README.html) in the Omnibus documentation. - -#### Test with GitLab development toolkits - -This is the less recommended approach, because it comes with a number of difficulties when emulating a real GitLab deployment. - -The [GDK](https://gitlab.com/gitlab-org/gitlab-development-kit) is not set up to run a Prometheus server or `node_exporter` alongside other GitLab components. If you would -like to do so, [Monitoring the GDK with Prometheus](https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/howto/prometheus/index.md#monitoring-the-gdk-with-prometheus) is a good start. - -The [GCK](https://gitlab.com/gitlab-org/gitlab-compose-kit) has limited support for testing Prometheus based Usage Ping. -By default, it already comes with a fully configured Prometheus service that is set up to scrape a number of components, -but with the following limitations: - -- It does not run a `gitlab-exporter` instance, so several `process_*` metrics from services such as Gitaly may be missing. -- While it runs a `node_exporter`, `docker-compose` services emulate hosts, meaning that it would normally report itself to not be associated -with any of the other services that are running. That is not how node metrics are reported in a production setup, where `node_exporter` -always runs as a process alongside other GitLab components on any given node. From Usage Ping's perspective none of the node data would therefore -appear to be associated to any of the services running, because they all appear to be running on different hosts. To alleviate this problem, the `node_exporter` in GCK was arbitrarily "assigned" to the `web` service, meaning only for this service `node_*` metrics appears in Usage Ping. - -## Aggregated metrics - -> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/45979) in GitLab 13.6. - -WARNING: -This feature is intended solely for internal GitLab use. - -To add data for aggregated metrics into Usage Ping payload you should add corresponding definition at [`config/metrics/aggregates/*.yaml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/aggregates/) for metrics available at Community Edition and at [`ee/config/metrics/aggregates/*.yaml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/metrics/aggregates/) for Enterprise Edition ones. - -Each aggregate definition includes following parts: - -- `name`: Unique name under which the aggregate metric is added to the Usage Ping payload. -- `operator`: Operator that defines how the aggregated metric data is counted. Available operators are: - - `OR`: Removes duplicates and counts all entries that triggered any of listed events. - - `AND`: Removes duplicates and counts all elements that were observed triggering all of following events. -- `time_frame`: One or more valid time frames. Use these to limit the data included in aggregated metric to events within a specific date-range. Valid time frames are: - - `7d`: Last seven days of data. - - `28d`: Last twenty eight days of data. - - `all`: All historical data, only available for `database` sourced aggregated metrics. -- `source`: Data source used to collect all events data included in aggregated metric. Valid data sources are: - - [`database`](#database-sourced-aggregated-metrics) - - [`redis`](#redis-sourced-aggregated-metrics) -- `events`: list of events names to aggregate into metric. All events in this list must - relay on the same data source. Additional data source requirements are described in the - [Database sourced aggregated metrics](#database-sourced-aggregated-metrics) and - [Redis sourced aggregated metrics](#redis-sourced-aggregated-metrics) sections. -- `feature_flag`: Name of [development feature flag](../feature_flags/index.md#development-type) - that is checked before metrics aggregation is performed. Corresponding feature flag - should have `default_enabled` attribute set to `false`. The `feature_flag` attribute - is optional and can be omitted. When `feature_flag` is missing, no feature flag is checked. - -Example aggregated metric entries: - -```yaml -- name: example_metrics_union - operator: OR - events: - - 'users_expanding_secure_security_report' - - 'users_expanding_testing_code_quality_report' - - 'users_expanding_testing_accessibility_report' - source: redis - time_frame: - - 7d - - 28d -- name: example_metrics_intersection - operator: AND - source: database - time_frame: - - 28d - - all - events: - - 'dependency_scanning_pipeline_all_time' - - 'container_scanning_pipeline_all_time' - feature_flag: example_aggregated_metric -``` - -Aggregated metrics collected in `7d` and `28d` time frames are added into Usage Ping payload under the `aggregated_metrics` sub-key in the `counts_weekly` and `counts_monthly` top level keys. - -```ruby -{ - :counts_monthly => { - :deployments => 1003, - :successful_deployments => 78, - :failed_deployments => 275, - :packages => 155, - :personal_snippets => 2106, - :project_snippets => 407, - :promoted_issues => 719, - :aggregated_metrics => { - :example_metrics_union => 7, - :example_metrics_intersection => 2 - }, - :snippets => 2513 - } -} -``` - -Aggregated metrics for `all` time frame are present in the `count` top level key, with the `aggregate_` prefix added to their name. - -For example: - -`example_metrics_intersection` - -Becomes: - -`counts.aggregate_example_metrics_intersection` - -```ruby -{ - :counts => { - :deployments => 11003, - :successful_deployments => 178, - :failed_deployments => 1275, - :aggregate_example_metrics_intersection => 12 - } -} -``` - -### Redis sourced aggregated metrics - -> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/45979) in GitLab 13.6. - -To declare the aggregate of events collected with [Redis HLL Counters](#redis-hll-counters), -you must fulfill the following requirements: - -1. All events listed at `events` attribute must come from - [`known_events/*.yml`](#known-events-are-added-automatically-in-usage-data-payload) files. -1. All events listed at `events` attribute must have the same `redis_slot` attribute. -1. All events listed at `events` attribute must have the same `aggregation` attribute. -1. `time_frame` does not include `all` value, which is unavailable for Redis sourced aggregated metrics. - -### Database sourced aggregated metrics - -> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/52784) in GitLab 13.9. -> - It's [deployed behind a feature flag](../../user/feature_flags.md), disabled by default. -> - It's enabled on GitLab.com. - -To declare an aggregate of metrics based on events collected from database, follow -these steps: - -1. [Persist the metrics for aggregation](#persist-metrics-for-aggregation). -1. [Add new aggregated metric definition](#add-new-aggregated-metric-definition). - -#### Persist metrics for aggregation - -Only metrics calculated with [Estimated Batch Counters](#estimated-batch-counters) -can be persisted for database sourced aggregated metrics. To persist a metric, -inject a Ruby block into the -[estimate_batch_distinct_count](#estimate_batch_distinct_count-method) method. -This block should invoke the -`Gitlab::Usage::Metrics::Aggregates::Sources::PostgresHll.save_aggregated_metrics` -[method](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage/metrics/aggregates/sources/postgres_hll.rb#L21), -which stores `estimate_batch_distinct_count` results for future use in aggregated metrics. - -The `Gitlab::Usage::Metrics::Aggregates::Sources::PostgresHll.save_aggregated_metrics` -method accepts the following arguments: - -- `metric_name`: The name of metric to use for aggregations. Should be the same - as the key under which the metric is added into Usage Ping. -- `recorded_at_timestamp`: The timestamp representing the moment when a given - Usage Ping payload was collected. You should use the convenience method `recorded_at` - to fill `recorded_at_timestamp` argument, like this: `recorded_at_timestamp: recorded_at` -- `time_period`: The time period used to build the `relation` argument passed into - `estimate_batch_distinct_count`. To collect the metric with all available historical - data, set a `nil` value as time period: `time_period: nil`. -- `data`: HyperLogLog buckets structure representing unique entries in `relation`. - The `estimate_batch_distinct_count` method always passes the correct argument - into the block, so `data` argument must always have a value equal to block argument, - like this: `data: result` - -Example metrics persistence: - -```ruby -class UsageData - def count_secure_pipelines(time_period) - ... - relation = ::Security::Scan.latest_successful_by_build.by_scan_types(scan_type).where(security_scans: time_period) - - pipelines_with_secure_jobs['dependency_scanning_pipeline'] = estimate_batch_distinct_count(relation, :commit_id, batch_size: 1000, start: start_id, finish: finish_id) do |result| - ::Gitlab::Usage::Metrics::Aggregates::Sources::PostgresHll - .save_aggregated_metrics(metric_name: 'dependency_scanning_pipeline', recorded_at_timestamp: recorded_at, time_period: time_period, data: result) - end - end -end -``` - -#### Add new aggregated metric definition - -After all metrics are persisted, you can add an aggregated metric definition at -[`aggregated_metrics/`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/aggregates/). - -To declare the aggregate of metrics collected with [Estimated Batch Counters](#estimated-batch-counters), -you must fulfill the following requirements: - -- Metrics names listed in the `events:` attribute, have to use the same names you passed in the `metric_name` argument while persisting metrics in previous step. -- Every metric listed in the `events:` attribute, has to be persisted for **every** selected `time_frame:` value. - -Example definition: - -```yaml -- name: example_metrics_intersection_database_sourced - operator: AND - source: database - events: - - 'dependency_scanning_pipeline' - - 'container_scanning_pipeline' - time_frame: - - 28d - - all -``` - -## Example Usage Ping payload - -The following is example content of the Usage Ping payload. - -```json -{ - "uuid": "0000000-0000-0000-0000-000000000000", - "hostname": "example.com", - "version": "12.10.0-pre", - "installation_type": "omnibus-gitlab", - "active_user_count": 999, - "recorded_at": "2020-04-17T07:43:54.162+00:00", - "edition": "EEU", - "license_md5": "00000000000000000000000000000000", - "license_id": null, - "historical_max_users": 999, - "licensee": { - "Name": "ABC, Inc.", - "Email": "email@example.com", - "Company": "ABC, Inc." - }, - "license_user_count": 999, - "license_starts_at": "2020-01-01", - "license_expires_at": "2021-01-01", - "license_plan": "ultimate", - "license_add_ons": { - }, - "license_trial": false, - "counts": { - "assignee_lists": 999, - "boards": 999, - "ci_builds": 999, - ... - }, - "container_registry_enabled": true, - "dependency_proxy_enabled": false, - "gitlab_shared_runners_enabled": true, - "gravatar_enabled": true, - "influxdb_metrics_enabled": true, - "ldap_enabled": false, - "mattermost_enabled": false, - "omniauth_enabled": true, - "prometheus_enabled": false, - "prometheus_metrics_enabled": false, - "reply_by_email_enabled": "incoming+%{key}@incoming.gitlab.com", - "signup_enabled": true, - "web_ide_clientside_preview_enabled": true, - "projects_with_expiration_policy_disabled": 999, - "projects_with_expiration_policy_enabled": 999, - ... - "elasticsearch_enabled": true, - "license_trial_ends_on": null, - "geo_enabled": false, - "git": { - "version": { - "major": 2, - "minor": 26, - "patch": 1 - } - }, - "gitaly": { - "version": "12.10.0-rc1-93-g40980d40", - "servers": 56, - "clusters": 14, - "filesystems": [ - "EXT_2_3_4" - ] - }, - "gitlab_pages": { - "enabled": true, - "version": "1.17.0" - }, - "container_registry_server": { - "vendor": "gitlab", - "version": "2.9.1-gitlab" - }, - "database": { - "adapter": "postgresql", - "version": "9.6.15", - "pg_system_id": 6842684531675334351 - }, - "analytics_unique_visits": { - "g_analytics_contribution": 999, - ... - }, - "usage_activity_by_stage": { - "configure": { - "project_clusters_enabled": 999, - ... - }, - "create": { - "merge_requests": 999, - ... - }, - "manage": { - "events": 999, - ... - }, - "monitor": { - "clusters": 999, - ... - }, - "package": { - "projects_with_packages": 999 - }, - "plan": { - "issues": 999, - ... - }, - "release": { - "deployments": 999, - ... - }, - "secure": { - "user_container_scanning_jobs": 999, - ... - }, - "verify": { - "ci_builds": 999, - ... - } - }, - "usage_activity_by_stage_monthly": { - "configure": { - "project_clusters_enabled": 999, - ... - }, - "create": { - "merge_requests": 999, - ... - }, - "manage": { - "events": 999, - ... - }, - "monitor": { - "clusters": 999, - ... - }, - "package": { - "projects_with_packages": 999 - }, - "plan": { - "issues": 999, - ... - }, - "release": { - "deployments": 999, - ... - }, - "secure": { - "user_container_scanning_jobs": 999, - ... - }, - "verify": { - "ci_builds": 999, - ... - } - }, - "topology": { - "duration_s": 0.013836685999194742, - "application_requests_per_hour": 4224, - "query_apdex_weekly_average": 0.996, - "failures": [], - "nodes": [ - { - "node_memory_total_bytes": 33269903360, - "node_memory_utilization": 0.35, - "node_cpus": 16, - "node_cpu_utilization": 0.2, - "node_uname_info": { - "machine": "x86_64", - "sysname": "Linux", - "release": "4.19.76-linuxkit" - }, - "node_services": [ - { - "name": "web", - "process_count": 16, - "process_memory_pss": 233349888, - "process_memory_rss": 788220927, - "process_memory_uss": 195295487, - "server": "puma" - }, - { - "name": "sidekiq", - "process_count": 1, - "process_memory_pss": 734080000, - "process_memory_rss": 750051328, - "process_memory_uss": 731533312 - }, - ... - ], - ... - }, - ... - ] - } -} -``` - -## Notable changes - -In GitLab 13.5, `pg_system_id` was added to send the [PostgreSQL system identifier](https://www.2ndquadrant.com/en/blog/support-for-postgresqls-system-identifier-in-barman/). - -## Exporting Usage Ping SQL queries and definitions - -Two Rake tasks exist to export Usage Ping definitions. - -- The Rake tasks export the raw SQL queries for `count`, `distinct_count`, `sum`. -- The Rake tasks export the Redis counter class or the line of the Redis block for `redis_usage_data`. -- The Rake tasks calculate the `alt_usage_data` metrics. - -In the home directory of your local GitLab installation run the following Rake tasks for the YAML and JSON versions respectively: - -```shell -# for YAML export -bin/rake gitlab:usage_data:dump_sql_in_yaml - -# for JSON export -bin/rake gitlab:usage_data:dump_sql_in_json - -# You may pipe the output into a file -bin/rake gitlab:usage_data:dump_sql_in_yaml > ~/Desktop/usage-metrics-2020-09-02.yaml -``` - -## Generating and troubleshooting usage ping - -This activity is to be done via a detached screen session on a remote server. - -Before you begin these steps, make sure the key is added to the SSH agent locally -with the `ssh-add` command. - -### Triggering - -1. Connect to bastion with agent forwarding: `$ ssh -A lb-bastion.gprd.gitlab.com` -1. Create named screen: `$ screen -S <username>_usage_ping_<date>` -1. Connect to console host: `$ ssh $USER-rails@console-01-sv-gprd.c.gitlab-production.internal` -1. Run `SubmitUsagePingService.new.execute` -1. Detach from screen: `ctrl + a, ctrl + d` -1. Exit from bastion: `$ exit` - -### Verification (After approx 30 hours) - -1. Reconnect to bastion: `$ ssh -A lb-bastion.gprd.gitlab.com` -1. Find your screen session: `$ screen -ls` -1. Attach to your screen session: `$ screen -x 14226.mwawrzyniak_usage_ping_2021_01_22` -1. Check the last payload in `raw_usage_data` table: `RawUsageData.last.payload` -1. Check the when the payload was sent: `RawUsageData.last.sent_at` +<!-- This redirect file can be deleted after <2021-10-09>. --> +<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page --> diff --git a/doc/development/usage_ping/metrics_dictionary.md b/doc/development/usage_ping/metrics_dictionary.md index 6b5fed4bcca..3743c2e0414 100644 --- a/doc/development/usage_ping/metrics_dictionary.md +++ b/doc/development/usage_ping/metrics_dictionary.md @@ -1,237 +1,9 @@ --- -stage: Growth -group: Product Intelligence -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments +redirect_to: '../service_ping/metrics_dictionary.md' +remove_date: '2021-10-09' --- -# Metrics Dictionary Guide +This file was moved to [another location](../service_ping/metrics_dictionary.md). -This guide describes Metrics Dictionary and how it's implemented - -## Metrics Definition and validation - -We are using [JSON Schema](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/schema.json) to validate the metrics definition. - -This process is meant to ensure consistent and valid metrics defined for Usage Ping. All metrics *must*: - -- Comply with the defined [JSON schema](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/schema.json). -- Have a unique `key_path` . -- Have an owner. - -All metrics are stored in YAML files: - -- [`config/metrics`](https://gitlab.com/gitlab-org/gitlab/-/tree/master/config/metrics) - -Each metric is defined in a separate YAML file consisting of a number of fields: - -| Field | Required | Additional information | -|---------------------|----------|----------------------------------------------------------------| -| `key_path` | yes | JSON key path for the metric, location in Usage Ping payload. | -| `name` | no | Metric name suggestion. Can replace the last part of `key_path`. | -| `description` | yes | | -| `product_section` | yes | The [section](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/sections.yml). | -| `product_stage` | no | The [stage](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/stages.yml) for the metric. | -| `product_group` | yes | The [group](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/stages.yml) that owns the metric. | -| `product_category` | no | The [product category](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/categories.yml) for the metric. | -| `value_type` | yes | `string`; one of [`string`, `number`, `boolean`, `object`](https://json-schema.org/understanding-json-schema/reference/type.html). | -| `status` | yes | `string`; [status](#metric-statuses) of the metric, may be set to `data_available`, `implemented`, `not_used`, `deprecated`, `removed`, `broken`. | -| `time_frame` | yes | `string`; may be set to a value like `7d`, `28d`, `all`, `none`. | -| `data_source` | yes | `string`; may be set to a value like `database`, `redis`, `redis_hll`, `prometheus`, `system`. | -| `data_category` | yes | `string`; [categories](#data-category) of the metric, may be set to `Operational`, `Optional`, `Subscription`, `Standard`. | -| `instrumentation_class` | no | `string`; [the class that implements the metric](metrics_instrumentation.md). | -| `distribution` | yes | `array`; may be set to one of `ce, ee` or `ee`. The [distribution](https://about.gitlab.com/handbook/marketing/strategic-marketing/tiers/#definitions) where the tracked feature is available. | -| `tier` | yes | `array`; may be set to one of `free, premium, ultimate`, `premium, ultimate` or `ultimate`. The [tier]( https://about.gitlab.com/handbook/marketing/strategic-marketing/tiers/) where the tracked feature is available. | -| `milestone` | no | The milestone when the metric is introduced. | -| `milestone_removed` | no | The milestone when the metric is removed. | -| `introduced_by_url` | no | The URL to the Merge Request that introduced the metric. | -| `repair_issue_url` | no | The URL of the issue that was created to repair a metric with a `broken` status. | -| `options` | no | `object`: options information needed to calculate the metric value. | -| `skip_validation` | no | This should **not** be set. [Used for imported metrics until we review, update and make them valid](https://gitlab.com/groups/gitlab-org/-/epics/5425). | - -### Metric statuses - -Metric definitions can have one of the following statuses: - -- `data_available`: Metric data is available and used in a Sisense dashboard. -- `implemented`: Metric is implemented but data is not yet available. This is a temporary - status for newly added metrics awaiting inclusion in a new release. -- `broken`: Metric reports broken data (for example, -1 fallback), or does not report data at all. A metric marked as `broken` must also have the `repair_issue_url` attribute. -- `not_used`: Metric is not used in any dashboard. -- `deprecated`: Metric is deprecated and possibly planned to be removed. -- `removed`: Metric was removed, but it may appear in Usage Ping payloads sent from instances running on older versions of GitLab. - -### Metric value_type - -Metric definitions can have one of the following values for `value_type`: - -- `boolean` -- `number` -- `string` -- `object`: A metric with `value_type: object` must have `value_json_schema` with a link to the JSON schema for the object. -In general, we avoid complex objects and prefer one of the `boolean`, `number`, or `string` value types. -An example of a metric that uses `value_type: object` is `topology` (`/config/metrics/settings/20210323120839_topology.yml`), -which has a related schema in `/config/metrics/objects_schemas/topology_schema.json`. - -### Metric time_frame - -- `7d`: The metric data applies to the most recent 7-day interval. For example, the following metric counts the number of users that create epics over a 7-day interval: `ee/config/metrics/counts_7d/20210305145820_g_product_planning_epic_created_weekly.yml`. -- `28d`: The metric data applies to the most recent 28-day interval. For example, the following metric counts the number of unique users that create issues over a 28-day interval: `config/metrics/counts_28d/20210216181139_issues.yml`. -- `all`: The metric data applies for the whole time the metric has been active (all-time interval). For example, the following metric counts all users that create issues: `/config/metrics/counts_all/20210216181115_issues.yml`. -- `none`: The metric collects a type of data that's not tracked over time, such as settings and configuration information. Therefore, a time interval is not applicable. For example, `uuid` has no time interval applicable: `config/metrics/license/20210201124933_uuid.yml`. - -### Metric name - -To improve metric discoverability by a wider audience, each metric with -instrumentation added at an appointed `key_path` receives a `name` attribute -filled with the name suggestion, corresponding to the metric `data_source` and instrumentation. -Metric name suggestions can contain two types of elements: - -1. **User input prompts**: Enclosed by `<>`, these pieces should be replaced or - removed when you create a metrics YAML file. -1. **Fixed suggestion**: Plaintext parts generated according to well-defined algorithms. - They are based on underlying instrumentation, and should not be changed. - -For a metric name to be valid, it must not include any prompt, and no fixed suggestions -should be changed. - -### Data category - -We use the following categories to classify a metric: - -- `Operational`: Required data for operational purposes. -- `Optional`: Data that is optional to collect. This can be [enabled or disabled](../usage_ping/index.md#disable-usage-ping) in the Admin Area. -- `Subscription`: Data related to licensing. -- `Standard`: Standard set of identifiers that are included when collecting data. - -### Metric name suggestion examples - -#### Metric with `data_source: database` - -For a metric instrumented with SQL: - -```sql -SELECT COUNT(DISTINCT user_id) FROM clusters WHERE clusters.management_project_id IS NOT NULL -``` - -- **Suggested name**: `count_distinct_user_id_from_<adjective describing: '(clusters.management_project_id IS NOT NULL)'>_clusters` -- **Prompt**: `<adjective describing: '(clusters.management_project_id IS NOT NULL)'>` - should be replaced with an adjective that best represents filter conditions, such as `project_management` -- **Final metric name**: For example, `count_distinct_user_id_from_project_management_clusters` - -For metric instrumented with SQL: - -```sql -SELECT COUNT(DISTINCT clusters.user_id) -FROM clusters_applications_helm -INNER JOIN clusters ON clusters.id = clusters_applications_helm.cluster_id -WHERE clusters_applications_helm.status IN (3, 5) -``` - -- **Suggested name**: `count_distinct_user_id_from_<adjective describing: '(clusters_applications_helm.status IN (3, 5))'>_clusters_<with>_<adjective describing: '(clusters_applications_helm.status IN (3, 5))'>_clusters_applications_helm` -- **Prompt**: `<adjective describing: '(clusters_applications_helm.status IN (3, 5))'>` - should be replaced with an adjective that best represents filter conditions -- **Final metric name**: `count_distinct_user_id_from_clusters_with_available_clusters_applications_helm` - -In the previous example, the prompt is irrelevant, and user can remove it. The second -occurrence corresponds with the `available` scope defined in `Clusters::Concerns::ApplicationStatus`. -It can be used as the right adjective to replace prompt. - -The `<with>` represents a suggested conjunction for the suggested name of the joined relation. -The person documenting the metric can use it by either: - -- Removing the surrounding `<>`. -- Using a different conjunction, such as `having` or `including`. - -#### Metric with `data_source: redis` or `redis_hll` - -For metrics instrumented with a Redis-based counter, the suggested name includes -only the single prompt to be replaced by the person working with metrics YAML. - -- **Prompt**: `<please fill metric name, suggested format is: {subject}_{verb}{ing|ed}_{object} eg: users_creating_epics or merge_requests_viewed_in_single_file_mode>` -- **Final metric name**: We suggest the metric name should follow the format of - `{subject}_{verb}{ing|ed}_{object}`, such as `user_creating_epics`, `users_triggering_security_scans`, - or `merge_requests_viewed_in_single_file_mode` - -#### Metric with `data_source: prometheus` or `system` - -For metrics instrumented with Prometheus or coming from the operating system, -the suggested name includes only the single prompt by person working with metrics YAML. - -- **Prompt**: `<please fill metric name>` -- **Final metric name**: Due to the variety of cases that can apply to this kind of metric, - no naming convention exists. Each person instrumenting a metric should use their - best judgment to come up with a descriptive name. - -### Example YAML metric definition - -The linked [`uuid`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/license/uuid.yml) -YAML file includes an example metric definition, where the `uuid` metric is the GitLab -instance unique identifier. - -```yaml -key_path: uuid -description: GitLab instance unique identifier -product_category: collection -product_section: growth -product_stage: growth -product_group: group::product intelligence -value_type: string -status: data_available -milestone: 9.1 -introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/1521 -time_frame: none -data_source: database -distribution: -- ce -- ee -tier: -- free -- premium -- ultimate -``` - -## Create a new metric definition - -The GitLab codebase provides a dedicated [generator](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/generators/gitlab/usage_metric_definition_generator.rb) to create new metric definitions. - -For uniqueness, the generated file includes a timestamp prefix, in ISO 8601 format. - -The generator takes the key path argument and 2 options and creates the metric YAML definition in corresponding location: - -- `--ee`, `--no-ee` Indicates if metric is for EE. -- `--dir=DIR` indicates the metric directory. It must be one of: `counts_7d`, `7d`, `counts_28d`, `28d`, `counts_all`, `all`, `settings`, `license`. - -```shell -bundle exec rails generate gitlab:usage_metric_definition counts.issues --dir=7d -create config/metrics/counts_7d/issues.yml -``` - -NOTE: -To create a metric definition used in EE, add the `--ee` flag. - -```shell -bundle exec rails generate gitlab:usage_metric_definition counts.issues --ee --dir=7d -create ee/config/metrics/counts_7d/issues.yml -``` - -## Metrics added dynamic to Usage Ping payload - -The [Redis HLL metrics](index.md#known-events-are-added-automatically-in-usage-data-payload) are added automatically to Usage Ping payload. - -A YAML metric definition is required for each metric. A dedicated generator is provided to create metric definitions for Redis HLL events. - -The generator takes `category` and `event` arguments, as the root key will be `redis_hll_counters`, and creates two metric definitions for weekly and monthly timeframes: - -```shell -bundle exec rails generate gitlab:usage_metric_definition:redis_hll issues i_closed -create config/metrics/counts_7d/i_closed_weekly.yml -create config/metrics/counts_28d/i_closed_monthly.yml -``` - -To create a metric definition used in EE, add the `--ee` flag. - -```shell -bundle exec rails generate gitlab:usage_metric_definition:redis_hll issues users_closing_issues --ee -create config/metrics/counts_7d/i_closed_weekly.yml -create config/metrics/counts_28d/i_closed_monthly.yml -``` +<!-- This redirect file can be deleted after <2021-10-09>. --> +<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page --> diff --git a/doc/development/usage_ping/metrics_instrumentation.md b/doc/development/usage_ping/metrics_instrumentation.md index ff0dbf99a09..f2d731803b8 100644 --- a/doc/development/usage_ping/metrics_instrumentation.md +++ b/doc/development/usage_ping/metrics_instrumentation.md @@ -1,102 +1,9 @@ --- -stage: Growth -group: Product Intelligence -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments +redirect_to: '../service_ping/metrics_instrumentation.md' +remove_date: '2021-10-09' --- -# Metrics instrumentation guide +This file was moved to [another location](../service_ping/metrics_instrumentation.md). -This guide describes how to develop Usage Ping metrics using metrics instrumentation. - -## Nomenclature - -- **Instrumentation class**: - - Inherits one of the metric classes: `DatabaseMetric`, `RedisHLLMetric` or `GenericMetric`. - - Implements the logic that calculates the value for a Usage Ping metric. - -- **Metric definition** - The Usage Data metric YAML definition. - -- **Hardening**: - Hardening a method is the process that ensures the method fails safe, returning a fallback value like -1. - -## How it works - -A metric definition has the [`instrumentation_class`](metrics_dictionary.md) field, which can be set to a class. - -The defined instrumentation class should have one of the existing metric classes: `DatabaseMetric`, `RedisHLLMetric`, or `GenericMetric`. - -Using the instrumentation classes ensures that metrics can fail safe individually, without breaking the entire - process of Usage Ping generation. - -We have built a domain-specific language (DSL) to define the metrics instrumentation. - -## Database metrics - -[Example of a merge request that adds a database metric](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60022). - -```ruby -module Gitlab - module Usage - module Metrics - module Instrumentations - class CountBoardsMetric < DatabaseMetric - operation :count - - relation { Board } - end - end - end - end -end -``` - -## Redis HyperLogLog metrics - -[Example of a merge request that adds a `RedisHLL` metric](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/61685). - -Count unique values for `i_quickactions_approve` event. - -```yaml -time_frame: 28d -data_source: redis_hll -instrumentation_class: 'Gitlab::Usage::Metrics::Instrumentations::RedisHLLMetric' -options: - events: - - i_quickactions_approve -``` - -## Generic metrics - -[Example of a merge request that adds a generic metric](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60256). - -```ruby -module Gitlab - module Usage - module Metrics - module Instrumentations - class UuidMetric < GenericMetric - value do - Gitlab::CurrentSettings.uuid - end - end - end - end - end -end -``` - -## Creating a new metric instrumentation class - -To create a stub instrumentation for a Usage Ping metric, you can use a dedicated [generator](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/generators/gitlab/usage_metric_generator.rb): - -The generator takes the class name as an argument and the following options: - -- `--type=TYPE` Required. Indicates the metric type. It must be one of: `database`, `generic`, `redis_hll`. -- `--ee` Indicates if the metric is for EE. - -```shell -rails generate gitlab:usage_metric CountIssues --type database - create lib/gitlab/usage/metrics/instrumentations/count_issues_metric.rb - create spec/lib/gitlab/usage/metrics/instrumentations/count_issues_metric_spec.rb -``` +<!-- This redirect file can be deleted after <2021-10-09>. --> +<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page --> diff --git a/doc/development/usage_ping/product_intelligence_review.md b/doc/development/usage_ping/product_intelligence_review.md index 0e86a116bca..dc51e3e300a 100644 --- a/doc/development/usage_ping/product_intelligence_review.md +++ b/doc/development/usage_ping/product_intelligence_review.md @@ -1,91 +1,9 @@ --- -stage: Growth -group: Product Intelligence -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments +redirect_to: '../service_ping/review_guidelines.md' +remove_date: '2021-10-09' --- -# Product Intelligence review guidelines +This file was moved to [another location](../service_ping/review_guidelines.md). -This page includes introductory material for a -[Product Intelligence](https://about.gitlab.com/handbook/engineering/development/growth/product-intelligence/) -review, and is specific to Product Intelligence reviews. For broader advice and -general best practices for code reviews, refer to our [code review guide](../code_review.md). - -## Resources for Product Intelligence reviewers - -- [Usage Ping Guide](index.md) -- [Snowplow Guide](../snowplow/index.md) -- [Metrics Dictionary](metrics_dictionary.md) - -## Review process - -We recommend a Product Intelligence review when an application update touches -Product Intelligence files. - -- Changes that touch `usage_data*` files. -- Changes to the Metrics Dictionary including files in: - - [`config/metrics`](https://gitlab.com/gitlab-org/gitlab/-/tree/master/config/metrics). - - [`ee/config/metrics`](https://gitlab.com/gitlab-org/gitlab/-/tree/master/ee/config/metrics). - - [`dictionary.md`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/usage_ping/dictionary.md). - - [`schema.json`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/schema.json). -- Changes to `tracking` files. -- Changes to Product Intelligence tooling. For example, - [`Gitlab::UsageMetricDefinitionGenerator`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/generators/gitlab/usage_metric_definition_generator.rb) - -### Roles and process - -#### The merge request **author** should - -- Decide whether a Product Intelligence review is needed. -- If a Product Intelligence review is needed, add the labels - `~product intelligence` and `~product intelligence::review pending`. -- Assign an - [engineer](https://gitlab.com/groups/gitlab-org/growth/product-intelligence/engineers/-/group_members?with_inherited_permissions=exclude) from the Product Intelligence team for a review. -- Set the correct attributes in YAML metrics: - - `product_section`, `product_stage`, `product_group`, `product_category` - - Provide a clear description of the metric. -- Update the - [Metrics Dictionary](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/usage_ping/dictionary.md) if it is needed. -- Add a changelog [according to guidelines](../changelog.md). - -##### When adding or modifying Snowplow events - -- For frontend events, when relevant, add a screenshot of the event in - the [testing tool](../snowplow/index.md#developing-and-testing-snowplow) used. -- For backend events, when relevant, add the output of the Snowplow Micro - good events `GET http://localhost:9090/micro/good` (it might be a good idea - to reset with `GET http://localhost:9090/micro/reset` first). - -#### The Product Intelligence **reviewer** should - -- Perform a first-pass review on the merge request and suggest improvements to the author. -- Approve the MR, and relabel the MR with `~"product intelligence::approved"`. - -## Review workload distribution - -[Danger bot](../dangerbot.md) adds the list of Product Intelligence changed files -and pings the -[`@gitlab-org/growth/product-intelligence/engineers`](https://gitlab.com/groups/gitlab-org/growth/product-intelligence/engineers/-/group_members?with_inherited_permissions=exclude) group for merge requests -that are not drafts. - -Any of the Product Intelligence engineers can be assigned for the Product Intelligence review. - -### How to review for Product Intelligence - -- Check the [metrics location](index.md#1-naming-and-placing-the-metrics) in - the Usage Ping JSON payload. -- Add `~database` label and ask for [database review](../database_review.md) for - metrics that are based on Database. -- For tracking using Redis HLL (HyperLogLog): - - Check the Redis slot. - - Check if a [feature flag is needed](index.md#recommendations). -- For tracking with Snowplow: - - Check that the [event taxonomy](../snowplow/index.md#structured-event-taxonomy) is correct. - - Check the [usage recommendations](../snowplow/index.md#usage-recommendations). -- Metrics YAML definitions: - - Check the metric `description`. - - Check the metrics `key_path`. - - Check the `product_section`, `product_stage`, `product_group`, `product_category`. - Read the [stages file](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/stages.yml). - - Check the file location. Consider the time frame, and if the file should be under `ee`. - - Check the tiers. +<!-- This redirect file can be deleted after <2021-10-09>. --> +<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page --> diff --git a/doc/development/usage_ping/review_guidelines.md b/doc/development/usage_ping/review_guidelines.md new file mode 100644 index 00000000000..dc51e3e300a --- /dev/null +++ b/doc/development/usage_ping/review_guidelines.md @@ -0,0 +1,9 @@ +--- +redirect_to: '../service_ping/review_guidelines.md' +remove_date: '2021-10-09' +--- + +This file was moved to [another location](../service_ping/review_guidelines.md). + +<!-- This redirect file can be deleted after <2021-10-09>. --> +<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page --> |