Closed joaquinsusin closed 9 months ago
Are you sure a Prometheus source has been added to Grafana? http://XX.XX.XX.XX:9182 implies windows_exporter
based on the port, not Prometheus.
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.
I have added the target with the ip and port of windows on my prometheus configuration file, but it is not showing the job name in the grafana server. But on prometheus server it is working fine.
Anyone please help me out here
@rahilk82 this sounds like an issue between Grafana and Prometheus, as you've mentioned that Prometheus is successfully scraping windows_exporter. You'll want to confirm connectivity between Grafana and Prometheus when adding the datasource in Grafana.
The node variables are different based on the OS. So due to hangover, I was trying to search Windows Node in Linux Dashboard. Sorry to disturb.
Hi. I am facing the same issue reported here. Prometheus is scrapping successfully from all my Nodes (which are Linux and Windows). I can see is working in Prometheus.
Now, in Grafana I only see the instances inside the job (is one job with many labeled instances) that are Linux Nodes, but the Windows ones does not appears.
Any ideas?
Hey so I have 2 ec2 instances one is a Prometheus Server with Grafana and the other one is a Windows client with windows exporter, the problem is that when I enter on prometheus and query something like windows_cpu_core_frequency_mhz I see results displaying but when I enter on grafana and add a source of prometheus with http://XX.XX.XX.XX:9182 it says Data source is working but when I try to display anything it says no data.
prometheus.yml
docker-compose.yml