Since monitoring is an application from the Rancher catalog, it can be configured like any other catalog application, by passing in values to Helm. To use this option, the nodes must have labels. Memory resource requests for the Prometheus pod.Ībility to select the nodes in which Prometheus and Grafana pods are deployed to. Memory resource limit for the Prometheus pod. Whether or not to configure storage for Grafana so that the Grafana dashboards and configuration can be retained even if the Grafana pod fails.ĬPU resource limit for the Prometheus pod. Whether or not to configure storage for Prometheus so that metrics can be retained even if the Prometheus pod fails. Required if you have enabled the node exporter. data that Prometheus collects from your node hardware. The host port on which data is exposed, i.e. Whether or not to deploy the node exporter. How long your Prometheus instance retains monitoring data scraped from Rancher objects before it's purged. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page.While configuring monitoring at either the cluster level or project level, there are multiple options that can be configured. The Linux Foundation has registered trademarks and uses trademarks. © Prometheus Authors 2014-2023 | Documentation Distributed under CC-BY-4.0 Please help improve it by filing issues or pull requests.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |