unable to add prometheus data source
jayeola opened this issue · 1 comments
jayeola commented
Hi,
Great work on this project! My problem is adding a prometheus data source.
Http settings:
URL == http://localhost:9090
Access == proxy
k8bctl logs -f [name-of--pod]
these are my errors. Can anyone give any pointers? Anyone else get this? Are there more steps to set up the prometheus data source?
t=2018-06-11T10:19:48+0000 lvl=info msg="Plugin dir created" logger=plugins dir=/var/lib/grafana/plugins
t=2018-06-11T10:19:48+0000 lvl=info msg="Initializing Stream Manager"
t=2018-06-11T10:19:48+0000 lvl=info msg="Initializing Alerting" logger=alerting.engine
t=2018-06-11T10:19:48+0000 lvl=info msg="Initializing CleanUpService" logger=cleanup
t=2018-06-11T10:19:48+0000 lvl=info msg="Initializing HTTP Server" logger=http.server address=0.0.0.0:3000 protocol=http subUrl=
t=2018-06-11T11:03:38+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=GET path=/ status=302 remote_addr=100.X.Y.Z time_ms=0s size=29
t=2018-06-11T11:10:48+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/api/v1/label/__name__/values status=502 remote_addr=100.X.Y.Z time_ms=8ns size=0
2018/06/11 11:10:48 http: proxy error: dial tcp [::1]:9090: getsockopt: connection refused
t=2018-06-11T11:12:29+0000 lvl=eror msg="Unable to call AWS API" logger=context userId=1 orgId=1 uname=admin error="MissingRegion: could not find region configuration"
t=2018-06-11T11:12:29+0000 lvl=eror msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/api/datasources/proxy/3 status=500 remote_addr=100.X.Y.Z time_ms=252ns size=36
2018/06/11 11:20:39 http: proxy error: dial tcp [::1]:8080: getsockopt: connection refused
t=2018-06-11T11:20:39+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/metrics/find status=502 remote_addr=100.X.Y.Z time_ms=2ns size=0
2018/06/11 11:20:52 http: proxy error: dial tcp [::1]:9090: getsockopt: connection refused
t=2018-06-11T11:20:52+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/api/v1/label/__name__/values status=502 remote_addr=100.X.Y.Z time_ms=2ns size=0
2018/06/11 11:20:53 http: proxy error: dial tcp [::1]:9090: getsockopt: connection refused
t=2018-06-11T11:20:53+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/api/v1/label/__name__/values status=502 remote_addr=100.X.Y.Z time_ms=2ns size=0
2018/06/11 11:20:54 http: proxy error: dial tcp [::1]:9090: getsockopt: connection refused
t=2018-06-11T11:20:54+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/api/v1/label/__name__/values status=502 remote_addr=100.X.Y.Z time_ms=2ns size=0
2018/06/11 11:22:06 http: proxy error: dial tcp [::1]:9090: getsockopt: connection refused
t=2018-06-11T11:22:06+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/api/v1/label/__name__/values status=502 remote_addr=100.X.Y.Z time_ms=2ns size=0
jayeola commented
closing issue. looks like prometheus is expecting the URL to be http://prometheus:9090, as mentioned in the README.
/me does not RTFM!!