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

# Monitoring

As operator you watch the two layers the DataOS runs on:

* DataOS Instance services
* Data Plane.

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

## Instance services

The **System Health** dashboard 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>/system-health/` and sign in with your Instance credentials. Status reads as:

| Status   | Meaning                            | Action                              |
| -------- | ---------------------------------- | ----------------------------------- |
| Healthy  | Check passed within threshold      | None                                |
| Degraded | Reachable but slow or intermittent | Review recent changes; inspect logs |
| Down     | Consecutive checks failed          | Follow runbooks; escalate if needed |

A useful ritual: open it at the start of the day, after any Instance change (confirm endpoints return to healthy), and when a user reports errors (check here first, then logs). Capture its state when you open an incident.

## Data Plane health

The System Health dashboard covers Instance services only. Data Product workload and Compute health on the Data Plane is watched separately, through the Operations application and Data Plane observability: are Computes healthy, are Data Product workloads scheduling, are Tenant runtime services up. Use this to confirm a Data Plane has capacity before you attach more Tenants to it, and to triage when a Tenant admin reports that Data Product workloads are not running.

What each role below you watches narrows from here: a [Tenant admin](/operate/v1/tenant-admin/monitoring.md) watches their Tenant's Compute and resources; a [developer](/operate/v1/data-developer/operate-your-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 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/dataos-operator/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.