Open Dentrax opened 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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Yes please!
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
/remove-lifecycle rotten /reopen
@Dentrax: Reopened this issue.
This would be great to have a starting point , is there any sample anyone can share ?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
Here's a very rough single-panel descheduler Grafana dashboard: https://gist.githubusercontent.com/aslafy-z/1a7f8cde84285bf578c9146dd95a9dcf/raw/eb50a0a0756de9076b97d0267322c87b170de51f/descheduler-grafana-dashboard.json
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
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?
@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.
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.
You're right, the query was missing a ~ to support multiple strategies. It's now fixed.
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
-