> 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.14/in-cluster-monitoring/monitoring-dashboard/monitoring-rules.md).
# Monitoring Rules
On the *Monitoring* > *Rules* page, we see a list of alerts that have been triggered and documented from a defined ruleset for a managed asset. It not only provides an overview, but also more in depth details. Options include selecting the name of the cluster, the severity level, and a search box to locate specific events or alerts.
The columns provide the following details about the alert messages.
* Name – The name of the triggered rule
* Severity – The importance of the notification
* Summary – A short synopsis of the code and a description of when the rule activated, the alert message itself, and what occurred to cause the problem
* Description – A characterization or encapsulation of the event
* Expressions – the alert values that are reported for the event
* Duration – The duration denotes the period of time in which the event transpired
* Cluster – This field states the cluster where the alert occurred.
Clicking on the alert name bring up a small pop-up window with further details.
These details include the following information.
* The name of the rule
* Its severity
* A short summary of the issue
* A description, if one exists
* The conditions which caused the alert
* The duration of the event
* Any labels that are applied
* Annotations or comments about the event.
---
# 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.14/in-cluster-monitoring/monitoring-dashboard/monitoring-rules.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.
