PRD: add Weekly Capacity Management Grafana dashboard#2604
Open
groundnuty wants to merge 1 commit into
Open
Conversation
Adds a new auto-loaded Grafana dashboard for PRD capacity tracking. The kube-prometheus-stack ArgoCD app already includes the directory ionos_prd/grafana-dashboards/ as a source, so the Grafana sidecar picks up new ConfigMaps with label grafana_dashboard=1 automatically. Stripped Grafana-export-only fields (id, uid, version) before embedding so the sidecar manages them on import. Verified locally with: kubectl --context dome-prod apply --dry-run=server -f <file> → configmap/weekly-capacity-management created (server dry run)
Contributor
|
Thanks! @groundnuty, can someone please approve the PR |
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.
Summary
Adds a new Grafana dashboard (created by @souviksengupta-ionos) for tracking weekly capacity in dome-prd. It will be picked up automatically by the existing
kube-prometheus-stackArgoCD app, which already watchesionos_prd/grafana-dashboards/as one of its sources.How it works
The dashboard is wrapped in a
ConfigMapwith labelgrafana_dashboard: "1". Grafana's sidecar inkube-prometheus-stackwatches for these labeled ConfigMaps cluster-wide and imports the dashboard JSON without restarting Grafana.This follows the exact same pattern used for the existing
ticketing-analytics.yamldashboard in the same directory.What was changed in the JSON before embedding
To avoid conflicts on import, the following Grafana-export-only fields were removed:
id(numeric ID, was41) — Grafana assigns one on importuid(wasafkjwa2n1kqgwc) — Grafana generates freshversion(was9) — Grafana tracks its own versionDatasource references use UID
prometheus, which is the same UID used by other prod dashboards (verified againstargocd-dashboard.yaml).Verification
kubectl --context dome-prod apply --dry-run=server \ -f ionos_prd/grafana-dashboards/weekly-capacity-management.yaml \ -n kube-prometheus-stack # configmap/weekly-capacity-management created (server dry run)Test plan
kube-prometheus-stackweekly-capacity-managementexists inkube-prometheus-stacknamespace