-
Notifications
You must be signed in to change notification settings - Fork 1.1k
201 - Prometheus not loading any metrics. #491
Comments
[UPDATE] I think the issue is just that prometheus-operator and prometheus are sharing the same RBAC here. While they should be different. I realized that as the API Servers appeared to be down (which happened because the I also hit this issue - You can just
Interestingly, these are not required according to the doc of 0.14.1 |
Can someone make the changes that @CharlyF mentioned? As of 7/14/18 this was still not working. |
I had the same issue and had to modify the cluster role.
|
And to be a little more precise—if you followed the directions in the guide, and you have a blank Targets page (and the prometheus container in the
After a couple minutes, you should start seeing Targets 'UP' in the Prometheus UI. I'll file a PR with this change, hopefully it can get merged soon! |
I'm currently following
https://github.com/aws-samples/aws-workshop-for-kubernetes/tree/master/02-path-working-with-clusters/201-cluster-monitoring
I've successfully loaded Prometheus in a browser after using the proxy command
kubectl port-forward $(kubectl get po -l prometheus=prometheus -n monitoring -o jsonpath={.items[0].metadata.name}) 9090 -n monitoring
but i am not seeing any of the metrics onlocalhost:9090
This is all I see:
![screen shot 2018-06-11 at 12 04 07 pm](https://user-images.githubusercontent.com/12597562/41243213-9e3e7384-6d6f-11e8-88ae-5d63194c2e90.png)
I have gone through 201 from the beginning twice, with the same results, following the cleanup shown at the end of the tutorial
Update
I just did some digging and noticed a lot of the following in the logs for the prometheus-prometheus-0 pod:
The text was updated successfully, but these errors were encountered: