> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/discover/search-the-hub/metrics.md).

# Metrics

Browse, filter, and preview the computed business measures available in a tenant.

A metric is a computed business measure defined on a Data Product's semantic layer, such as `active_customers` or `customer_lifetime_value`. Metrics let you find a ready-made value without building a query.

## Switch the scope to Metrics

On the Hub, select the arrow next to the **Data Products** title and choose **Metrics**. The Hub lists the metrics in the tenant as cards, grouped by domain. Each domain heading shows how many metrics it holds; select **View all** next to a domain to see every metric in it.

![Metrics listing with filters and metrics grouped by domain](https://540997223-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAxLuoblPBpNVcNU4lKPo%2Fuploads%2Fgit-blob-acf2e53f12859141700ea88306518fd7ae4880fe%2Fhub-metrics-by-domain.png?alt=media)

Each card shows the metric name, a short description of what it measures, the Data Product it belongs to, and its glossary terms (the first term, then **+N more**).

## Choose a view

* **All:** every metric in the tenant.
* **Favorites:** the metrics you starred.
* **My metrics:** only your metrics.

## Filter

Use **Search for metrics** to match by keyword, and the filters next to it to narrow the list:

* **Domain:** metrics from one business area.
* **Terms:** metrics linked to a glossary term.
* **Tags:** your team's conventions. The dropdown has a search box and includes system tags.
* **Data Product:** only metrics from the product you care about.
* **Owner:** metrics maintained by a person you trust or can ask.

A filter applies as soon as you select a value; there is no separate apply step. A dot marks each active filter, the Hub shows the result count, and **Reset all** clears every filter. See [Filters](https://v2.dataos.info/consume/discover/search-the-hub/filters.md).

## Open one

Select a metric to open its context card, a quick summary that helps you confirm it fits before you use it. From the context card, open the metric's details, or explore it directly in the [Studio query interface](https://v2.dataos.info/consume/evaluate/query-in-studio.md).

Explore more: [Explore assets](https://v2.dataos.info/consume/evaluate/assets.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://v2.dataos.info/consume/discover/search-the-hub/metrics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
