Merge pull request #3744 from jtravee/monitoringV2-CPU

Updated Monitoring v2 docs to account for higher CPU usage.
This commit is contained in:
Billy Tat authored and GitHub committed 2022-01-03 16:28:49 -08:00
commit 21cf894066
2 files changed
+4

No files matched your search

@@ -15,6 +15,8 @@ For information on configuring custom scrape targets and rules for Prometheus, p
The resource requests and limits for the monitoring application can be configured when installing `rancher-monitoring`. For more information about the default limits, see [this page.](./helm-chart-options/#configuring-resource-limits-and-requests)
>**Note:** On an idle cluster, Monitoring V2 has significantly higher CPU usage (up to 70%) as compared to Monitoring V1. To improve performance and achieve similar results as in Monitoring V1, turn off the Prometheus adapter.
# Prometheus Configuration
It is usually not necessary to directly edit the Prometheus custom resource.
@@ -11,6 +11,8 @@ For information on configuring custom scrape targets and rules for Prometheus, p
The resource requests and limits for the monitoring application can be configured when installing `rancher-monitoring`. For more information about the default limits, see [this page.](./helm-chart-options/#configuring-resource-limits-and-requests)
>**Note:** On an idle cluster, Monitoring V2 has significantly higher CPU usage (up to 70%) as compared to Monitoring V1. To improve performance and achieve similar results as in Monitoring V1, turn off the Prometheus adapter.
# Prometheus Configuration
It is usually not necessary to directly edit the Prometheus custom resource.