You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Rancher installation and the entire Kube-Prometheus stack was installed from outside and not through the Rancher console, because the monitoring stack was consuming a lot of resources through Rancher. Anyway, I installed the stack and was able to monitor everything, except for some components such as kube-scheduler, kube-proxy and kubecontrollermanager. I saw that Rancher uses pushprox to monitor these components. I even found a chart that Rancher itself provides, but I didn't understand how to monitor these components using the same helm chart and even seeing the official documentation here, I found it very superficial. can anybody help me?
The text was updated successfully, but these errors were encountered:
I have a Rancher installation and the entire Kube-Prometheus stack was installed from outside and not through the Rancher console, because the monitoring stack was consuming a lot of resources through Rancher. Anyway, I installed the stack and was able to monitor everything, except for some components such as kube-scheduler, kube-proxy and kubecontrollermanager. I saw that Rancher uses pushprox to monitor these components. I even found a chart that Rancher itself provides, but I didn't understand how to monitor these components using the same helm chart and even seeing the official documentation here, I found it very superficial. can anybody help me?
The text was updated successfully, but these errors were encountered: