Hi Julius ! Thanks for amazing videos. I'm doing a project for my postgraduate in which I've install minikube and running a docker container based service on my local host 3001. The service is accessible through web browser and perfectly working. I want to enable this service monitoring enable at Prometheus but state shows down at localhost:9090/target even though ive mentioned localhot:3001 as my target under scrape configs. I'm pretty confused what to do ? should I enable any other option ? please guide ?
Hi Julis, I'm having trouble fetching metrics from the target host RHEL 8. I've installed the Node Exporter on RHEL and it's running fine. I've verified the metrics using the navigator, and they seem to be working. However, when I declared the host from my Ubuntu server to Prometheus, the targets always show as down, with no host detected. (no rout )
Hi! For specific scenario support questions like that, it's usually better to reach out to one of the public community channels (for example, the users mailing list is great for getting competent answers from people). See prometheus.io/community/
hello Julius, Thanks for this great explaining. I actually have a problem when scrape any port except the main port for prometheus (9090), for example: port 9100 for node-exporter or any other port and it always has down state. could you please tell me how could i fix this problem
Not sure what the problem is here if you checked that the network connectivity from Prometheus to the other process works and that the port is specific in the target. But generally it's a good idea to ask with more details on the users mailing list (see prometheus.io/community/).
Amazing!
Great tutorial
Thank you so much
Hi Julius ! Thanks for amazing videos. I'm doing a project for my postgraduate in which I've install minikube and running a docker container based service on my local host 3001. The service is accessible through web browser and perfectly working. I want to enable this service monitoring enable at Prometheus but state shows down at localhost:9090/target even though ive mentioned localhot:3001 as my target under scrape configs. I'm pretty confused what to do ? should I enable any other option ? please guide ?
Thank you for the tutorial, you are definitely the best fit to explain Prometheus & Grafana. Thank you simplifying soo much the explanation
Wow, thank you so much for the compliment, I'm so glad you liked it! :)
Hi Julis, I'm having trouble fetching metrics from the target host RHEL 8. I've installed the Node Exporter on RHEL and it's running fine. I've verified the metrics using the navigator, and they seem to be working. However, when I declared the host from my Ubuntu server to Prometheus, the targets always show as down, with no host detected. (no rout )
Hi! For specific scenario support questions like that, it's usually better to reach out to one of the public community channels (for example, the users mailing list is great for getting competent answers from people). See prometheus.io/community/
hello Julius, Thanks for this great explaining. I actually have a problem when scrape any port except the main port for prometheus (9090), for example: port 9100 for node-exporter or any other port and it always has down state. could you please tell me how could i fix this problem
Not sure what the problem is here if you checked that the network connectivity from Prometheus to the other process works and that the port is specific in the target. But generally it's a good idea to ask with more details on the users mailing list (see prometheus.io/community/).
I'm watching your tutorial at 3:50 AM and having my head racked for 2 weeks thanks 🧍