Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customize default graph selections in monitoring section #10655

Open
eberhab opened this issue Mar 20, 2024 · 0 comments
Open

Customize default graph selections in monitoring section #10655

eberhab opened this issue Mar 20, 2024 · 0 comments
Labels
area/monitoring kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this

Comments

@eberhab
Copy link

eberhab commented Mar 20, 2024

Hi everyone,

We are running Rancher 2.7 and just installed the monitoring (prometheus-operator/kube-prometheus) chart for our clusters. After installing the monitoring chart, the dashboard displays a pre-defined set of Grafana graphs oob. While this is very convenient and basically happens at the push of a single button, the default selection of graphs isn’t what we usually want to see and we’d like to modify the selection.

In more detail: After installing the prom monitoring chart, the Rancher cluster dashboard offers the following manual customization options: [“Cluster Metrics”, “Kubernetes Components Metrics”, “Etcd Metrics”], {“Range”: “5m”, “Refresh”: “30s”}. We would like to permanently define these values to always display the “Cluster Metrics” of the last “1h” Range and refresh only every “5m”.

The current solution is to perform the selection by hand, at the time we open the dashboard. Preferably there would be a configmap or such, to re-define these defaults which are currently hardcoded.

Your consideration would be much appreciated!

@github-actions github-actions bot added [zube]: To Triage QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this and removed [zube]: To Triage labels Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/monitoring kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

4 participants