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
The bottom three IPs are prometheus. However, I can get onto the EC2 instance hosting the rancher-windows-exporter pod and curl http://localhost:9796/metrics and can get all the metrics. If I exec into another node in any namespace and curl the EC2 instance primary IP such as http://10.136.111.222:9796/metrics it works. The servicemonitor picks up the IP of the pod running rancher-windows-exporter which doesn't work.
The text was updated successfully, but these errors were encountered:
Rancher windows exporter is running AWS EKS with wins version 0.1.3. However, we see the following with exporter-node-proxy:
The bottom three IPs are prometheus. However, I can get onto the EC2 instance hosting the rancher-windows-exporter pod and curl http://localhost:9796/metrics and can get all the metrics. If I exec into another node in any namespace and curl the EC2 instance primary IP such as http://10.136.111.222:9796/metrics it works. The servicemonitor picks up the IP of the pod running rancher-windows-exporter which doesn't work.
The text was updated successfully, but these errors were encountered: