kubernetes-sigs / descheduler

Descheduler for Kubernetes
https://sigs.k8s.io/descheduler
Apache License 2.0
4.47k stars 668 forks source link

Create and publish official Grafana Dashboard #1046

Open Dentrax opened 1 year ago

Dentrax commented 1 year ago

Is your feature request related to a problem? Please describe. People may be taking the time to make their own dashboards. (at least we did last year). We can provide an out-of-box Grafana Dashboard.

Describe the solution you'd like Create and maintain the official Deschduler Grafana dashboard in this repo and publish it to Grafana Dashboard Marketplace

Add the Dashboard link in the README.

Describe alternatives you've considered -

Additional context -

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

WDaan commented 1 year ago

Yes please!

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/descheduler/issues/1046#issuecomment-1615861922): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ 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.
Dentrax commented 1 year ago

/remove-lifecycle rotten /reopen

k8s-ci-robot commented 1 year ago

@Dentrax: Reopened this issue.

In response to [this](https://github.com/kubernetes-sigs/descheduler/issues/1046#issuecomment-1671404278): >/remove-lifecycle rotten >/reopen 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.
samavasi commented 10 months ago

This would be great to have a starting point , is there any sample anyone can share ?

k8s-triage-robot commented 7 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 6 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

aslafy-z commented 6 months ago

/remove-lifecycle rotten

aslafy-z commented 6 months ago

Here's a very rough single-panel descheduler Grafana dashboard: https://gist.githubusercontent.com/aslafy-z/1a7f8cde84285bf578c9146dd95a9dcf/raw/eb50a0a0756de9076b97d0267322c87b170de51f/descheduler-grafana-dashboard.json

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

aslafy-z commented 3 months ago

/remove-lifecycle stale

mrclrchtr commented 2 months ago

Here's a very rough single-panel descheduler Grafana dashboard: https://gist.githubusercontent.com/aslafy-z/1a7f8cde84285bf578c9146dd95a9dcf/raw/eb50a0a0756de9076b97d0267322c87b170de51f/descheduler-grafana-dashboard.json

Hi @aslafy-z, is this dashboard working for you?

aslafy-z commented 1 month ago

@mrclrchtr I updated a the query with a missing field, however, it's just a filter. It works for me for version v0.26.0. Updated version at https://gist.github.com/aslafy-z/1a7f8cde84285bf578c9146dd95a9dcf.

mrclrchtr commented 1 month ago

Thank you. I have tried it and unfortunately it only works for me if you explicitly select a strategy. If I deselect the filter, it shows nothing.

After changing the query to: sum(descheduler_pods_evicted{namespace=~"$namespace",strategy=~"$strategy"}) by (namespace,strategy,result) (="$strategy" -> =~"$strategy") it's always showing some data.

aslafy-z commented 1 month ago

You're right, the query was missing a ~ to support multiple strategies. It's now fixed.