From e216da10e6151eb0faa2f3f481d8a9908cb1b3ae Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Thu, 16 Dec 2021 17:48:43 -0500 Subject: [PATCH 1/4] 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. From 684b6c4048afdafa7caea6cc96494c24686e2efa Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Thu, 16 Dec 2021 17:49:12 -0500 Subject: [PATCH 2/4] Added note about V2 CPU usage in 2.6 --- .../rancher/v2.6/en/monitoring-alerting/configuration/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/rancher/v2.6/en/monitoring-alerting/configuration/_index.md b/content/rancher/v2.6/en/monitoring-alerting/configuration/_index.md index 078bf7f31e4..e8204151ee9 100644 --- a/content/rancher/v2.6/en/monitoring-alerting/configuration/_index.md +++ b/content/rancher/v2.6/en/monitoring-alerting/configuration/_index.md @@ -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) +>**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. From 3f50f33ca3bf06d0a0dbad3a2c7a7d648029bfe6 Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Tue, 21 Dec 2021 10:49:43 -0500 Subject: [PATCH 3/4] Updated note with workaround for 2.5 --- .../rancher/v2.5/en/monitoring-alerting/configuration/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 350c18172f2..2d7867cbc4c 100644 --- a/content/rancher/v2.5/en/monitoring-alerting/configuration/_index.md +++ b/content/rancher/v2.5/en/monitoring-alerting/configuration/_index.md @@ -15,7 +15,7 @@ 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. +>**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 From 0b136bd4b2a81727f095b0212482a4e53fbd8142 Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Tue, 21 Dec 2021 10:49:59 -0500 Subject: [PATCH 4/4] Updated note with workaround for 2.6 --- .../rancher/v2.6/en/monitoring-alerting/configuration/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/monitoring-alerting/configuration/_index.md b/content/rancher/v2.6/en/monitoring-alerting/configuration/_index.md index e8204151ee9..876031fb4d7 100644 --- a/content/rancher/v2.6/en/monitoring-alerting/configuration/_index.md +++ b/content/rancher/v2.6/en/monitoring-alerting/configuration/_index.md @@ -11,7 +11,7 @@ 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. +>**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