Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upNot able to use nodeport to get metrics from node-exporter endpoints port #5237
Comments
dcvtruong
changed the title
Not able to use nodeport for node-exporter endpoints port
Not able to use nodeport to get metrics from node-exporter endpoints port
Feb 19, 2019
This comment has been minimized.
This comment has been minimized.
|
Thanks for your report. It looks as if this is actually a question about usage and not development. To make your question, and all replies, easier to find, we suggest you move this over to our user mailing list, which you can also search. If you prefer more interactive help, join or our IRC channel, #prometheus on irc.freenode.net. Please be aware that our IRC channel has no logs, is not searchable, and that people might not answer quickly if they are busy or asleep. If in doubt, you should choose the mailing list. Once your questions have been answered, please add a short line pointing to relevant replies in case anyone stumbles here via a search engine in the future. |
simonpasquier
closed this
Feb 21, 2019
This comment has been minimized.
This comment has been minimized.
|
Hi, This is not a question about usage. This is an actual problem not able to use nodeport port to forward to node-exporter exposed port 9100. |
dcvtruong commentedFeb 19, 2019
•
edited
Bug Report
What did you do?
Using nodeport to get metrics from node-exporter port 9100 from outside the container
What did you expect to see?
Able to retrieve node-exporter metrics using nodeport port like this "curl http://endpoints_ip:nodeport_port/metrics"
What did you see instead? Under which circumstances?
timeout from the curl command
Environment
System information:
Linux 3.10.0-957.1.3.el7.x86_64 x86_64
K8s 1.13
Prometheus version:
Prometheus 2.6.1
Alertmanager version:
not relevant to the issue
Prometheus configuration file: