> 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/dataos-operator/monitoring.md).

# Monitoring

Watch the Instance Status page and Data Plane health from the Operator's seat.

As Operator you watch the two layers DataOS runs on:

* DataOS Instance services
* Data Plane

{% hint style="info" %}
To understand the shared Observability model and its layers, see the [Observability model](https://v2.dataos.info/operate/observability-model.md).
{% endhint %}

## Instance services

The [Instance Status page](https://v2.dataos.info/operate/instance-status.md) is your first stop for whether Instance services are up. It runs active health checks against Instance endpoints and reports availability, response time, certificate validity, and recent pass/fail history.

Open it at `https://<instance-fqdn>/status/` and sign in. For what each status means, when to check the page, and what to do when a service is Degraded or Down, see [DataOS Instance Status](https://v2.dataos.info/operate/instance-status.md).

## Data Plane health

The Instance Status page covers Instance services only. Watch Data Product workload and Compute health separately through the Operations application and Data Plane observability:

* Are Computes healthy?
* Are Data Product workloads scheduling?
* Are Tenant runtime services up?

Use these signals to:

* Confirm Data Plane capacity before attaching more Tenants.
* Triage reports that Data Product workloads are not running.

What each role watches narrows from here:

* A Tenant Admin [monitoring.md](https://v2.dataos.info/operate/tenant-admin/monitoring.md) watches their Tenant's compute and resources.
* A Data Developer [Monitor Data Product](https://v2.dataos.info/operate/data-developer/monitor-data-product.md) watches their product's runs.
* You watch the planes and DataOS Instance services that everything else depends on.


---

# 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/operate/dataos-operator/monitoring.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.
