search

kubernetes-retired / heapster

[EOL] Compute Resource Usage Analysis and Monitoring of Container Clusters
Apache License 2.0
2.63k stars 1.25k forks source link

Grafana do not have cluster and pods dashboards after I build a new docker image #2039

Closed owenJiao closed 6 years ago

owenJiao commented 6 years ago

I tried to build a new grafana image, when I ran it in a pod, the status of this pod is running ,but when I opened the browser, I found there were not pod and cluster list in dashboards, and I checked the log, there is no error message showed in log file. so could you tell me where I should notice?

lvicentesanchez commented 6 years ago

Grafana dashboards are not persistent across restarts of the pod; I had to use a database as my dashboard backend.

fejta-bot commented 6 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

ttarczynski commented 6 years ago

Is it maybe the same issue as #2013 ?

SFHfeihong commented 6 years ago

I have same problem. The version of grafana is v5.0.4.

wu105 commented 6 years ago

For new clusters installations getting grafana v5.0.4, the grafana does not provide any pre-loaded dashboards. With grafana v4.4.3 we used previuosly, dashboards cluster and pod are pre-loaded.

Our work around is to save the dashboards from clusters that do have the cluster and pod dashboards as json files, and import them into the new cluster's grafana.

New heapster versions should continue to include clulster and pod as built in dashboard as earlier versions. If someone knows good dashboards for kubernetes on grafana.com, please share with us. I tried quite a few and still prefer the cluster and pod dashboards.

fejta-bot commented 6 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

fejta-bot commented 6 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close

k8s-ci-robot commented 6 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes/heapster/issues/2039#issuecomment-442245564): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
wu105 commented 6 years ago

/reopen /remove-lifecycle rotten

wu105 commented 6 years ago

compared with #2013, this thread points an issue showed up between v4.4.3 and v5.0.4 and contains a workaround by saving the dashboards from clusters that do have the cluster and pod dashboards as json files, and import them into the new cluster's grafana.