feat: add control and custom quota grafana dashboards - #2111
Open
yindia wants to merge 1 commit into
Open
Conversation
Signed-off-by: Yuvraj <evalsocket@gmail.com>
yindia
force-pushed
the
feat/issue-1925
branch
from
August 31, 2026 13:44
8f16c58 to
9088a74
Compare
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two built-in operational Grafana dashboards to the Helm chart, covering resource health and custom quota consumption. They drop into
charts/capsule/dashboardsand are rendered by the existing dashboards ConfigMap template, gated behindmonitoring.dashboards.enabled. No controller, template, or dependency changes are needed.capsule-controlcapsule_*_condition(generic{__name__=~"capsule_.+_condition"}),capsule_tenant_namespace_countcapsule-customquotacapsule_custom_quota_resource_*,capsule_global_custom_quota_resource_*The Control dashboard queries conditions by metric name pattern, so it automatically covers every condition family that exists now or is added later, without per kind maintenance.
Everything was validated end to end against a live controller in a kind cluster with kube-prometheus-stack: resources applied from
example/, metrics scraped through a ServiceMonitor into Prometheus, and both dashboards loaded into Grafana and confirmed to populate with real data.Fixes #1925