> 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/observability/system-health-dashboards.md).

# System Health Dashboards

The DataOS Instance Status page shows the current status of configured Instance services.

Use this page to check whether Instance services are operational, degraded, or unavailable.

## Why it is useful

Use the DataOS Instance Status page when you need to quickly check the current status of Instance services.

For example, if users report that a DataOS application is unavailable or slow, this page can help you confirm whether any Instance-level service is showing an issue before you look at Tenant configuration, workload logs, or external systems.

***

## Access the status page

* Open the following path on your DataOS Instance:

`https://<instance-fqdn>/status/`

Replace `<instance-fqdn>` with your DataOS Instance domain.

**Example:**

`https://pacific-051426.dataos.cloud/status/`

If prompted, sign in using your DataOS credentials or SSO. After sign-in, the DataOS Instance Status page opens.


---

# 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/observability/system-health-dashboards.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.