From 3d8ecce3a6ff7868ad941db3500e286645c90998 Mon Sep 17 00:00:00 2001
From: Denise <denise@rancher.com>
Date: Thu, 21 Mar 2019 13:24:42 -0700
Subject: [PATCH] Update _index.md

---
 content/rancher/v2.x/en/tools/monitoring/_index.md | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/content/rancher/v2.x/en/tools/monitoring/_index.md b/content/rancher/v2.x/en/tools/monitoring/_index.md
index aaedc2193fc..8c6f3acaee9 100644
--- a/content/rancher/v2.x/en/tools/monitoring/_index.md
+++ b/content/rancher/v2.x/en/tools/monitoring/_index.md
@@ -68,16 +68,23 @@ You can deploy Prometheus monitoring for a cluster, navigate to **Tools > Monito
 
 Following Prometheus deployment, two monitoring applications are added to the cluster's `system` project's **Apps** page: `cluster-monitoring` and `monitoring-operator`. You can use the `cluster-monitoring` catalog app to [access the Grafana instance](#grafana-accessing-for-clusters) for the cluster.
 
-When enabling cluster level monitoring, resources should be allocated to the Prometheus pod based on the number of nodes. The control plane and etcd nodes should also be counted in the number. The table below provides a guide for the ammount of resources that should be planned for the Prometheus pod, when enabling cluster monitoring. Total disk space allocation should be approximated by the `rate * retention` period set at the cluster level.
+### Resource Consumption
 
+When enabling cluster level monitoring, you will need to ensure your worker nodes and Prometheus pod have enough resources. The tables below provides a guide of how much resource consumption will be used. 
 
-Number of Cluster Nodes | CPU(milli CPU) | Memory | Disk 
+#### Prometheus Pod Resource Consumption
+
+This table is the resource consumption of the Prometheus pod, which is based on the number of all the nodes in the cluster. The count of nodes includes the worker, control plane and etcd nodes. Total disk space allocation should be approximated by the `rate * retention` period set at the cluster level. When enabling cluster level monitoring, you should adjust the CPU and Memory limits and reservation. 
+
+Number of Cluster Nodes | CPU (milli CPU) | Memory | Disk 
 ------------------------|-----|--------|------
 5 | 500 | 650 MB | ~1 GB/Day
 50| 2000 | 2 GB | ~5 GB/Day
 256| 4000 | 6 GB | ~18 GB/Day
 
-Additionally, the following components will be deployed when cluster monitoring is enabled and consume approximately the following amount of resources.
+#### Other Pods Resource Consumption
+
+Besides the Prometheus pod, there are components that are deployed that require additional resources on the worker nodes.
 
 Pod | CPU (milli CPU) | Memory (MB)
 ----|-----------------|------------
@@ -86,7 +93,6 @@ Kube State Cluster Monitor | 100 | 130
 Grafana | 100 | 150
 Prometheus Cluster Monitoring Nginx | 50 | 50
 
-
 ## Configuring Project Monitoring
 
 You can enable project monitoring by opening the project and then selecting **Tools > Monitoring** as shown in the GIF below, which displays enabling the `default` project monitoring.