> 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/overview.md).

# Overview

Discovery is the first step in the consumer journey. It helps you find the right Data Product, Perspective, or Metric for a business, analytical, operational, or technical goal before you spend time reviewing details, querying outputs, or connecting downstream tools.

In DataOS, discovery starts in the Hub. There, you can search, filter, and preview available Data Products in the selected Tenant. You can also switch the search scope to **Perspectives** - saved, governed query views and **Metrics** - computed business measures.

## What to discover

You can start with a known Data Product name, a domain, a tag, or an intent. For example, to find customer and order analytics, search for an Order 360 Data Product, review its summary, and confirm that it covers your use case. You can also switch the search scope to Metrics to find a specific business measure directly, or browse Perspectives to find a reusable saved query that already answers the question.

Discovery should answer these questions:

| Question                                                           | Why it matters                                                              |
| ------------------------------------------------------------------ | --------------------------------------------------------------------------- |
| Is there a Data Product for the use case?                          | Confirms whether a governed product already exists.                         |
| Does the product name, description, or tag match the intent?       | Helps narrow the available products to a relevant option.                   |
| Is there a Metric that already tracks the business measure I need? | Lets you use a ready-made computed value without building a query.          |
| Is there a Perspective that already answers the question I have?   | Lets you reuse a saved, governed query view instead of building a new one.  |
| Who owns or maintains the product?                                 | Identifies the right team or owner for questions and support.               |
| Is the product relevant enough to review in detail?                | Determines whether to continue to understanding, querying, or consuming it. |

## Discovery paths

Use the discovery path that matches how you want to start:

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Search the Hub</strong><br>When you know part of what you need, browse, search, filter, and preview to land on the right Data Product.</td><td><a href="/pages/X4Rwz6ciKzseYlZCYmGc">/pages/X4Rwz6ciKzseYlZCYmGc</a></td></tr><tr><td><strong>Search in natural language</strong><br>When you only know your intent, describe it in natural language and let DataOS surface matching Data Products.</td><td><a href="/pages/Jl86Vdl9NrOQ9r7vaFFA">/pages/Jl86Vdl9NrOQ9r7vaFFA</a></td></tr></tbody></table>


---

# 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/overview.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.