> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/semantic-intelligence/metrics-catalog.md).

# Metrics Catalog

The Metrics Catalog lists every metric [Semantic Intelligence](https://docs.datalogz.io/guides/semantic-intelligence.md) analyzed for the selected connector and team.

| Column               | Description                                                       |
| -------------------- | ----------------------------------------------------------------- |
| **Measure**          | The metric name.                                                  |
| **Type**             | The kind of metric: for example "measure" or "calculated column". |
| **Department**       | Department of the semantic model.                                 |
| **Data model**       | The semantic model the metric lives in.                           |
| **Table**            | The table the metric is defined on.                               |
| **Business concept** | The concept the metric was grouped into.                          |

Click a row to open the metric's detail panel, with its type, department, data model, table, business concept, the expression as written and the expanded expression.

You can also reach Semantic Intelligence from [Inventory](https://docs.datalogz.io/guides/inventory.md): on a semantic model or similar asset page, the **Data Attributes** tab has an **Open in Semantic Intelligence** link.


---

# 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://docs.datalogz.io/guides/semantic-intelligence/metrics-catalog.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.
