-
Notifications
You must be signed in to change notification settings - Fork 960
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
Some dashboard panel selectors missing #4164
Comments
Hi, thanks for filing the issue. Can you send a pr, please? |
I'd fix the dashboard, which selectors do you find fitting? Should the advanced metrics panel group also filter based on the instance label? To me it would be more usable if i could see the metrics of all pods of the same cluster at the same time. What do you think? |
Where do you take this dashboard, actually? Is it from https://github.com/dragonflydb/dragonfly/tree/main/tools/local/monitoring ? |
yes, that is the one |
So this one it totally for the community to decide. I mainly use it for local development, so I do not have strong opinions. |
@Pothulapati , @Abhra303 - what do you think? |
pls check it out if you are interested: https://github.com/dragonflydb/dragonfly/pull/4165/files |
I would still be interested to know from community side if there is anything against adjusting the dashboard so that we see metrics for the whole cluster and don't have to select a specific pod from the statefulset. IMHO that makes sense to get a good overview about what is going on in the cluster (but still grouping metrics by pod). |
Describe the bug
The following panels are missing any selector, which makes the dashboard consider dragonfly instances from other namespaces:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I should not see metrics from different namespaces, as those must by definiton be a different cluster.
Would be nice to have dragonfly clusters emit a label
cluster
which would be used to select metrics of a specific cluster.That would make having multiple clusters in the same namespace possible too.
Screenshots
The text was updated successfully, but these errors were encountered: