Prerequisite: Need a remote storage endpoint to be available.Gathering CPU, memory, network and other resource usage at a machine level isĬrucial when monitoring an infrastructure. When enabling persistent storage for Prometheus or Grafana, specify the size of the persistent volume and select the StorageClass. With the external persistent storage, if the Prometheus or Grafana pods fail, the new pods can recover using data from the persistent storage. Rancher recommends configuring an external persistent storage to the cluster. With local storage, if the Prometheus or Grafana pods fail, all the data is lost. Prerequisite: Configure one or more StorageClasses to use as persistent storage for your Prometheus or Grafana pod.īy default, when you enable Prometheus for either a cluster or project, all monitoring data that Prometheus collects is stored on its own pod. By default, 9796 is used as that host port. Warning: In order for Prometheus to collect the metrics of the node exporter, after enabling cluster monitoring, you must open the Node Exporter Host Port in the host firewall rules to allow intranet access. The host port chosen must be open to allow internal traffic between Prometheus and the Node Exporter. When configuring Prometheus and enabling the node exporter, enter a host port in the Node Exporter Host Port that will not produce port conflicts with existing applications. In order to monitor actual network metrics for the container network, the node exporter must be deployed with the hostNetwork mode. However, there are still issues with namespaces when running it in a container, mostly around filesystem mount spaces. It is designed to monitor the host system. The node exporter is a popular open source exporter, which exposes the metrics for hardware and *NIX kernels OS. Some example key-value pairs are: Variable Prometheus LivenessProbe and ReadinessProbe can be configured as custom answers in the Advanced Options section. The Prometheus operator documentation contains the full RemoteReadSpec and RemoteWriteSpec.Īn example configuration would be: Variable Prometheus RemoteRead and RemoteWrite can be configured as custom answers in the Advanced Options section.įor more information on remote endpoints and storage, refer to the Prometheus documentation. Warning: Any modification to the application without understanding the entire application can lead to catastrophic errors. 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. While configuring monitoring at either the cluster level or project level, there are multiple options that can be configured.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |