is grafana dashboard UI on localhost:3000?

[giantswarm]

is grafana dashboard UI on localhost:3000?

[giulioroggero]

@jerrwy you should use this URL for proxy after the run of kubectl proxy

http://127.0.0.1:8001/api/v1/namespaces/monitoring/services/http:grafana:/proxy

In that way you are calling service http:grafana and you are asking a proxy on it

[pipo02mix]

If you are running it in minkube you have to expose the grafana service (Nodeport type) or run a kubectl proxy

[jerrwy]

i had run kubectl proxy
when i visit http://localhost:8001/api/v1/namespaces/monitoring/services/grafana:3000
i get result

{
	"kind": "Status",
	"apiVersion": "v1",
	"metadata": {},
	"status": "Failure",
	"message": "services \"grafana:3000\" not found",
	"reason": "NotFound",
	"details": {
		"name": "grafana:3000",
		"kind": "services"
	},
	"code": 404
}

how can i visit grafana dashboard UI ?

[giulioroggero]

If you still have problems another approach is to go directly to pod without proxy

Run
kubectl port-forward $(kubectl get pods --selector=app=grafana -n monitoring --output=jsonpath="{.items..metadata.name}") -n monitoring 9200:3000

and then go to

http://localhost:9200

[jerrwy]

thx! it worked!

[jerrwy]

how can i visit prometheus targets in kubectl proxy?
i have try http://127.0.0.1:8001/api/v1/namespaces/monitoring/services/http:prometheus:/proxy
but return result

{
	"kind": "Status",
	"apiVersion": "v1",
	"metadata": {},
	"status": "Failure",
	"message": "no endpoints available for service \"http:prometheus:\"",
	"reason": "ServiceUnavailable",
	"code": 503
}

[jerrwy]

thx~ i am use kubectl port-forward command visit prometheus targets now

[pipo02mix]

Yeah, port forward should be the way in case you don't expose it through an ingress resource. Adding this info in the readme