You are viewing documentation for a previous version of Platform9 products. For the latest Private Cloud Director documentation, click here.
Search
Managed Kubernetes
5.14
×
Overview
Getting Started
Clusters
PMK CLI
APIs
In Cluster Monitoring
Catapult Remote Monitoring
Platform9 Managed Add-ons
Platform Administration
Workloads & Apps
Support
Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Troubleshooting Monitoring Slow Startup
Summarize Page
Copy Markdown
Open in ChatGPT
Open in Claude
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?
To ensure Platform9 Monitoring deploys and starts in a timely manner we recommended the following minimum requirements are met:
Single Node Clusters
Bash
* Run with at least 4 CPUs and 16 GB of RAMMulti-Node Clusters
Bash
* Run all nodes with 4 CPUs and 8GB of RAMType to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Last updated on
Was this page helpful?
Next to read:
AWS TroubleshootingDiscard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message