Updating Handbook references from Data Catalog to Data Guides

description: "Data Governance Processes and Workflows at GitLab"

---

- [Data Catalog](/handbook/enterprise-data/data-governance/data-catalog)

- [Data Guides](/handbook/enterprise-data/data-governance/data-catalog)

- [Data Quality](/handbook/enterprise-data/data-governance/data-quality)

- [Data Management](/handbook/enterprise-data/data-governance/data-management)

---

title: "Data Catalog"

description: "The Data Catalog page indexes Analytics Dashboards, Workflows, and Terms."

---

title: "Data Guides"

description: "The Data Guides page indexes Analytics Dashboards, Workflows, and Terms."

---

## Purpose

The purpose of this **Data Catalog** is to help you understand and make use of the data that is available in our [Snowflake Data Warehouse](/handbook/enterprise-data/platform/) for reporting and analysis. The **Data Catalog** is available in our [Internal GitLab Handbook](https://internal.gitlab.com/handbook/enterprise-data/data-governance/data-catalog/).

The purpose of this **Data Guides** is to help you understand and make use of the data that is available in our [Snowflake Data Warehouse](/handbook/enterprise-data/platform/) for reporting and analysis. The **Data Guides** is available in our [Internal GitLab Handbook](https://internal.gitlab.com/handbook/enterprise-data/data-governance/data-catalog/).

Here are some useful links that we recommend for you to bookmark:

- [Data Catalog](https://internal.gitlab.com/handbook/enterprise-data/data-governance/data-catalog/): Helpful guides on how to use our data

- [Data Guides](https://internal.gitlab.com/handbook/enterprise-data/data-governance/data-catalog/): Helpful guides on how to use our data

- [DBT documentation](https://dbt.gitlabdata.com/#!/overview): Data model documentation

- [Service Ping Metrics Dictionary](https://metrics.gitlab.com/): Service Ping metric definitions and metadata

- [Service Ping documentation](https://docs.gitlab.com/ee/development/internal_analytics/service_ping/)

   Option B: Use Usage Data Instrumentation Issue Template to outline metric requirements

   - Use the [Usage Data Instrumentation Issue Template](https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Usage%2520Data%2520Instrumentation) 

   Tag your [assigned product analyst](/handbook/product/groups/product-analysis/#team-members) to review metric properties

   - Tag your [assigned product analyst](/handbook/product/groups/product-analysis/#team-members) to review metric properties

1. Implement Tracking

## Helpful places to start

- [Internal handbook performance indicators (PIs)](https://internal.gitlab.com/handbook/company/performance-indicators/) - This internal handbook page is a great place to understand the PIs for each Stage / Group to understand what results each team is trying to acheive.

- [Internal handbook performance indicators (PIs)](https://internal.gitlab.com/handbook/company/performance-indicators/) - This internal handbook page is a great place to understand the PIs for each Stage / Group to understand what results each team is trying to achieve.

- [Product categories handbook page](/handbook/product/categories/) contains a huge amount of helpful information and defines sections, stages, groups, and categories.

- [Features by Group handbook page](/handbook/product/categories/features/#product-planning) contains a tabular breakdown of features included in each Stage Group by Core, Premium or Ultimate categories.

- [Definitive guides to data subject areas](/handbook/enterprise-data/data-governance/data-catalog) managed by the Data team.

- [Data Guides](/handbook/enterprise-data/data-governance/data-catalog) managed by the Data team.

- [Centralized Metrics](https://10az.online.tableau.com/#/site/gitlab/workbooks/2069845/views): Key reporting dashboard for GitLab product usage metrics.

- common_mart.mart_ping_instance_metric_28_day - Use for 28 day timeframe metrics

- common_mart.mart_ping_instance_metric_monthly - Use for all, 7, 28 timeframe metrics pre filtered to the last ping of the month (does not include none or null timeframe metrics)

- common_mart.mart_ping_instance_metric_monthly - Use for all, 7, 28 timeframe metrics pre-filtered to the last ping of the month (does not include none or null timeframe metrics)

- workpace_product.wk_fct_ping_instance_metric_none - Use for metrics with a none timeframe

### Growth Section

Although the [Growth Section](/handbook/marketing/growth/) falls within the Maketing & Strategy division, the Growth Section has dedicated support from Product Data Insights on topics within our ownership areas.

Although the [Growth Section](/handbook/marketing/growth/) falls within the Marketing & Strategy division, the Growth Section has dedicated support from Product Data Insights on topics within our ownership areas.

#### Growth Stage (Acquisition, Activation Groups)

- [SaaS Team Activation](https://docs.google.com/presentation/d/1rJG8FaqEjfgA-Nz9Ww3blgcUwRGzri7CeKkn1e2eEHY/edit?usp=sharing)

- [Valuable Signup](https://docs.google.com/presentation/d/1xHBrnvwdMxQGqmX0TtcQz5tUYsAeU6CAMnpcDlhHUpc/edit?usp=sharing)

- [Valuable Sign-up](https://docs.google.com/presentation/d/1xHBrnvwdMxQGqmX0TtcQz5tUYsAeU6CAMnpcDlhHUpc/edit?usp=sharing)

- Both of the above metrics are monitored in [Growth Section Product Data Insights Hub in Tableau](https://10az.online.tableau.com/t/gitlab/views/GrowthSectionProductDataInsightsHub/GrowthSectionProductDataInsightsHub)

- [DBT Docs](https://dbt.gitlabdata.com/#!/overview) - This resource contains comprehensive documentation on all available dbt models. When in doubt, search DBT!

- [Data guides to data subject areas](https://internal.gitlab.com/handbook/enterprise-data/data-governance/data-catalog/) managed by the Data team.

- [Data Guides](https://internal.gitlab.com/handbook/enterprise-data/data-governance/data-catalog/) to understand enterprise analytics subject areas that are broadly useful to the GitLab organization; managed by the Data team.

- [Documentation on data pipelines](/handbook/enterprise-data/platform/pipelines/) for the technically curious analyst. This page goes into each data source and extraction details.

- [Table of data sources and refresh schedules](/handbook/enterprise-data/platform/#data-sources) to understand standard load times for each data source.

- [Enterprise Data Data Catalog](https://internal.gitlab.com/handbook/enterprise-data/data-governance/data-catalog/) to understand enterprise analytics subject areas that are broadly useful to the GitLab organization.

## Data Model Categories

These categories are grouped by data source and subject area.

#### FAQs

> Why doesn't the metric that my team implememented show up in the [metrics dictionary](https://metrics.gitlab.com/snowplow)?

> Why doesn't the metric that my team implemented show up in the [metrics dictionary](https://metrics.gitlab.com/snowplow)?

- In order to show up in the [metrics dictionary](https://metrics.gitlab.com/snowplow), every event needs a [.yml file](https://gitlab.com/gitlab-org/gitlab/-/tree/master/config/events). This will not happen automatically and should be created by the engineer that implements snowplow tracking.

<details markdown="1"><summary>Click to expand</summary>

- If you are wondering if Snowplow events are implemented in a certain area of the product, the [Snowplow Inspector](https://chrome.google.com/webstore/detail/snowplow-inspector/maplkdomeamdlngconidoefjpogkmljm?hl=en) is a good complimentary resource to the [Metrics Dicitonary](https://metrics.gitlab.com/) which is not exhaustive. The Snowplow Inspector will not show server side events.

- If you are wondering if Snowplow events are implemented in a certain area of the product, the [Snowplow Inspector](https://chrome.google.com/webstore/detail/snowplow-inspector/maplkdomeamdlngconidoefjpogkmljm?hl=en) is a good complimentary resource to the [Metrics Dictionary](https://metrics.gitlab.com/) which is not exhaustive. The Snowplow Inspector will not show server side events.

- We do not use snowplow on our self-managed instances, only on GitLab.com

> What is a namespace?

- Starting with the basics! GitLab has two categories of namespaces; groups and projects. In general, a namespace provides one place to organize your related projects. Read more [here](https://docs.gitlab.com/user/namespace/). Namespaces exist within GitLab SaaS and Self-Managed products, but to product the privacy of our Self-Managed users, we only collect identifiable namespace data for SaaS.

- Starting with the basics! GitLab has two categories of namespaces; groups and projects. In general, a namespace provides one place to organize your related projects. Read more [here](https://docs.gitlab.com/user/namespace/). Namespaces exist within GitLab SaaS and Self-Managed products, but to protect the privacy of our Self-Managed users, we only collect identifiable namespace data for SaaS.

> What types of namespaces do we normally analyze?

#### FAQs

> When can we report total deduped users across all Duo features?

> When can we report total de-duped users across all Duo features?

- Complete deduped totals across all features and deployment types are only available starting August 3rd, 2024. Historical data availability varies by feature and deployment type.

- Complete de-duped totals across all features and deployment types are only available starting August 3rd, 2024. Historical data availability varies by feature and deployment type.

> How is Duo usage attributed to customers?