> 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

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 consumers find a ready-made value without building a query.

This page covers how to **discover** Metrics from the Hub.

## Switch the search scope to Metrics

By default the Hub lists Data Products. To browse Metrics, open the scope selector using the icon next to the search field and choose **Metrics**.

<img src="/files/SbV4gfbUh6D4movfK71u" alt="Search scope selector with Metrics selected" width="375">

The Hub then lists the Metrics available in the selected Tenant as cards. Each card shows the Metric icon, its name, and a short description of what it measures, so you can spot a ready-made measure without writing a query.

<figure><img src="/files/Kwy9azOdzTcQBk1DabUZ" alt="Hub listing Metrics as cards with the filter panel on the left"><figcaption><p>The Hub with the search scope set to Metrics.</p></figcaption></figure>

## Filter Metrics

When many Metrics exist, the **Filter by** panel helps you reach the right measure faster. Narrow the list by:

* **Data Product**: see only Metrics from the product you care about.
* **Tags**: group Metrics by the conventions your team uses.
* **Owner**: find Metrics maintained by a specific person you trust or can ask.

You can combine filters with keyword search to narrow the list further. See [Filters](/consume/discover/search-the-hub/filters.md) for how the filter panel works.

## Open a Metric

Click a Metric in the list to open its detail panel on the right and confirm it fits before you use it. The panel shows:

* **Description**: what the Metric measures, so you can confirm it matches the business question you have.
* **Composition**: the measure, dimensions, and time field that make up the Metric, so you know exactly how the value is calculated.
* **Product**: the Data Product the Metric belongs to, so you can trace it to a trusted source.
* **Owner**: the user who owns the Metric, so you know who to ask about it.
* **Tag(s)**: the tags applied to the Metric, which place it within your team's conventions.

<figure><img src="/files/9HpMqEDLWaQnqV9oaWPl" alt="Metric detail panel showing description, composition, product, owner, and tags"><figcaption><p>The Metric detail panel.</p></figcaption></figure>

Select **Open in Studio** to explore the Metric further in the Studio query interface.

## Explore more

* [Perspectives](/consume/discover/search-the-hub/perspectives.md)
* [Query in Studio](/consume/understand/overview.md)
* [Explore assets](/consume/understand/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
