> 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.15/catapult-remote-monitoring/catapult-remote-monitoring.md).

# Catapult Remote Monitoring

Catapult remote monitoring provides 24/7 coverage of every cluster managed by Platform9. Catapult is purpose built to monitor critical cluster and application services and alert both Platform9 Support and Cluster Operations teams of issues and outages. Catapult leverages Prometheus in Agent Mode and is installed automatically onto each node that is part of the cluster. The data collected is streamed back to the SaaS Management Plane where over 50 prebuilt Prometheus rules operate to send out notifications to email, Slack and more.

#### Catapult Monitoring Rules Overview <a href="#catapult-monitoring-rules-overview" id="catapult-monitoring-rules-overview"></a>

The following rules are built into Catapult and operate within the SaaS Management Plane.

* [etcd Monitoring](/managed-kubernetes/5.15/catapult-remote-monitoring/catapult-rules-alarms/etcd-monitoring.md)
* [Kubernetes API Monitoring](/managed-kubernetes/5.15/catapult-remote-monitoring/catapult-rules-alarms/kubernetes-monitoring.md)
* [Kube State Monitoring](/managed-kubernetes/5.15/catapult-remote-monitoring/catapult-rules-alarms/kube-state--monitoring.md)
* [Node OS Monitoring](/managed-kubernetes/5.15/catapult-remote-monitoring/catapult-rules-alarms/node-os-monitoring.md)
* [Environment Status](/managed-kubernetes/5.15/catapult-remote-monitoring/catapult-rules-alarms/environment-status-monitoring.md)
* [Node Connectivity Monitoring](/managed-kubernetes/5.15/catapult-remote-monitoring/catapult-rules-alarms/nodes-connectivity-monitoring.md)
* [Platform9 Managed Add-on Monitoring](/managed-kubernetes/5.15/catapult-remote-monitoring/catapult-rules-alarms/addons-catapult.md)

#### Catapult Architecture <a href="#catapult-architecture" id="catapult-architecture"></a>

<figure><img src="https://914468382-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdN3UKqOJY9TdzQV1eEIf%2Fuploads%2Fx5FuONddoXCkgCWHq7OU%2Fimage.png?alt=media&amp;token=5eebffe9-74e1-4484-95f1-7874c957ffb7" alt=""><figcaption></figcaption></figure>


---

# 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.15/catapult-remote-monitoring/catapult-remote-monitoring.md?ask=<question>&goal=<user_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.