> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-kubernetes/5.9/monitoring-dashboard/monitoring-overview.md).
# Monitoring Overview
When the Monitoring tab is selected in the UI, the overview page is shown. It contains a dropdown menu for severity and priority. Also noted is a graphical overview showing the number of Fatal, Critical, and Warnings along with the total number of alarms. Clicking the circular icon refreshes the page. Above that are quick links to Grafana and the *Infrastructure* > *Cluster* (link) > *Nodes* page.
On the far-right side, we see and can easily sort Healthy Clusters and Clusters Without Monitoring. Under the Healthy Clusters are quick links to Grafana and the *Infrastructure* > *Cluster* (link) > *Nodes* page.
---
# 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.platform9.com/managed-kubernetes/5.9/monitoring-dashboard/monitoring-overview.md?ask=&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.
