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 upCannot get other information targets scrapped except kubernetes-nodes (kubernetes_sd_config) #2189
Comments
sudhirpandey
changed the title
Cannot get other information targets scrapped expect kubernetes-nodes
Cannot get other information targets scrapped except kubernetes-nodes (kubernetes_sd_config)
Nov 14, 2016
This comment has been minimized.
This comment has been minimized.
|
i realised that i was missing kubernetes_sd_confius on job_name kubernetes-apiservers , so i added this under the job, which resulted the api end servers to be found.
But i still cannot the other service, endpoints and pod roles to work. I amd hoping they will also show up as different targets via their job name in prometheus UI. |
This comment has been minimized.
This comment has been minimized.
|
The config looks ok, do the logs say anything? Also make sure your |
This comment has been minimized.
This comment has been minimized.
|
Thanks . Also seems to need to be running the blackbox exporter pod to get the probe part to work. i applied this annonations in the service
and have following yaml to take care of the blackbox service to do probing
And was able to get the desired service end point to be monitored. |
This comment has been minimized.
This comment has been minimized.
|
We have and are compiling Kubernetes + Prometheus resources at kube-prometheus. The problem with the example config is that it is a bit limit and opinionated. But I understand that some more explanation would have helped. I'll come up with something to make it easier for the next to come. Thanks for the feedback! |
This comment has been minimized.
This comment has been minimized.
|
Thanks the resources indeed seems to be helpful. Thanks for the help :) |
sudhirpandey
closed this
Nov 16, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |

sudhirpandey commentedNov 14, 2016
•
edited
What did you do?
Upgrade the openshift origin to 1.3 and prometheus to 1.3.1
What did you expect to see?
different job-names targets should have been visible under status > targets
What did you see instead? Under which circumstances?
Environment
promethes v1.3.1
uname -srm
With the configuration in place i expect to see services and endpoints.. but also the cluster api as well ..but in web UI of prometheus i just get results from job name kubernetes-nodes

I have used promethes 1.2.1 with origin 1.2.0 and i was able to get api-endpoints metrics as well. Is there any debug level info i can look at to figure out what really going on.