From e216da10e6151eb0faa2f3f481d8a9908cb1b3ae Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Thu, 16 Dec 2021 17:48:43 -0500 Subject: [PATCH] Added note about V2 CPU usage in 2.5 --- .../rancher/v2.5/en/monitoring-alerting/configuration/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/rancher/v2.5/en/monitoring-alerting/configuration/_index.md b/content/rancher/v2.5/en/monitoring-alerting/configuration/_index.md index e56978fbb98..350c18172f2 100644 --- a/content/rancher/v2.5/en/monitoring-alerting/configuration/_index.md +++ b/content/rancher/v2.5/en/monitoring-alerting/configuration/_index.md @@ -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) +>**Warning:** On an idle cluster, Monitoring V2 has significantly higher CPU usage (up to 70%) as compared to Monitoring V1. + # Prometheus Configuration It is usually not necessary to directly edit the Prometheus custom resource.