> 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.10/monitoring-dashboard.md).
# Monitoring Dashboard
The PMK Monitoring dashboard is a real-time multi cluster view into alarms for the last 24 hours. Using this dashboard you are able to filter alarms by `severity`, `cluster` and `time`. Each alarm contains a link to drill down to Grafana for further investigation.
#### My Monitoring Dashboard is Empty?
For the Monitoring Dashboard to populate at lease one cluster within your environment must have monitoring enabled.
To ensure monitoring is enabled navigate to `Infrastructure` click the `Clusters` tab and then select a cluster, this will activate the table toolbar, then click the `Monitoring` button. In the popup click `Enable`.
Once enabled the Platform9 Management Plan will then deploy an `Operator` that runs Prometheus, Alertmanager and Grafana.
{% hint style="warning" %}
**Warning**
Depending on the clusters available resources the `Operator` may take up to 15 minutes to start all required `Pods`.
{% endhint %}
For the full guidance on enabling monitoring, refer to [auto$](https://github.com/platform9/pcd-docs-gitbook/blob/main/kubernetes/enabling-in-cluster-monitoring/README.md).
---
# 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.10/monitoring-dashboard.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.
