public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update _index.md

Browse Source
This commit is contained in:
Denise
2019-03-22 10:25:30 -07:00
committed by Denise Schannon
parent d3be347c82
commit 3d8ecce3a6
1 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/tools/monitoring/_index.md
+10 -4
View File
@@ -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.