> 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/operate/v1/data-admin/monitoring.md).

# Monitoring

Your monitoring scope is the Lakehouse: is it healthy, performing, and being used as intended. The shared [Observability model](/operate/v1/observability-model.md) places this alongside the tenant admin's resource view.

## What to watch

* **Service health.** The Lakehouse runs a catalog and query services; confirm they are up and responsive. Failures here surface to every product that reads or writes the Lakehouse.
* **Metastore health.** The PostgreSQL catalog metastore is the Lakehouse's source of truth for table metadata. Watch its availability and growth; a metastore problem looks like tables "disappearing" or scans failing.
* **Storage growth and table sprawl.** Track object-storage growth and the number of tables and snapshots. Iceberg accumulates snapshots; plan maintenance so storage and query planning stay efficient.
* **Usage.** Which namespaces and tables are queried, and by whom, tells you what to optimize and what is abandoned.

## Operating practices

* **Set a maintenance rhythm** for Iceberg tables (snapshot expiry, compaction) so query planning and storage stay healthy as data grows.
* **Watch the metastore database** you dedicated to the Lakehouse; it is the single most important dependency.
* **Tie usage back to structure.** Heavily queried tables may deserve their own optimization; unused ones are candidates for retirement after checking with their owners.

When a problem is Instance-wide rather than Lakehouse-specific, escalate to the [tenant admin](/operate/v1/tenant-admin/monitoring.md) or [operator](/operate/v1/dataos-operator/monitoring.md), whose scopes sit above the Lakehouse.


---

# 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/operate/v1/data-admin/monitoring.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.