# Troubleshooting Monitoring Slow Startup

During testing of the Monitoring deployment process it has been found that clusters with limited resources or deployments running as a single-node cluster may experience delays in launching Monitoring. In rare occasions that the entire infrastructure running the cluster is restarted, Monitoring may experience delays starting.

#### How to improve startup? <a href="#how-to-improve-startup" id="how-to-improve-startup"></a>

To ensure Platform9 Monitoring deploys and starts in a timely manner we recommended the following minimum requirements are met:

#### Single Node  <a href="#single-node-clusters" id="single-node-clusters"></a>

#### Clusters <a href="#single-node-clusters" id="single-node-clusters"></a>

```
* Run with at least 4 CPUs and 16 GB of RAM
```

#### Multi-Node Clusters <a href="#multi-node-clusters" id="multi-node-clusters"></a>

```
* Run all nodes with 4 CPUs and 8GB of RAM
```


---

# Agent Instructions: 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:

```
GET https://docs.platform9.com/managed-kubernetes/support/troubleshooting/troubleshooting-monitoring-slow-startup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.