You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest making the job label, e.g. for the Kubernetes API Server a variable that can be set during the kustomize call or make the hard-coded Regex more flexible.
For instance, there is the following query for the API Server:
I agree, the current regex isn't very flexible...
How about creating a job variable for the k8s-system-api-server dashboard?
That should make it even more flexible!
That's a great idea! I just came up with the "quick fix". But having a job variable (which is also used in other dashboards) would be great. Currently I have a scenario where I play around with different dashboards, including yours, but also the Kubernetes Mixins and Boards from Grafana Mimir.
I believe it will be a swift PR on your side. I would declare myself still a rookie when it comes to Grafana dashboards, but I'd be happy to send you early feedback before merging into main.
Describe the enhancement you'd like
I suggest making the job label, e.g. for the Kubernetes API Server a variable that can be set during the kustomize call or make the hard-coded Regex more flexible.
For instance, there is the following query for the API Server:
My API Server metrics us "kube-apiserver" for the job label. So, I cannot see this metric in the provided dashboard.
I'd suggest to make it look more like this:
This would match the following job labels:
Additional context
No response
The text was updated successfully, but these errors were encountered: