grafana-platform-dashboardlisted

# Grafana Platform Dashboard Design platform operations dashboards so operators see tenant-impacting risk first, then drill into service-specific health without overload. ## Quick Start Use this skill when the user asks for platform dashboard updates and reliability checks. 1. Confirm dashboard target: ```bash oc --context <ctx> get grafanadashboard -A | rg -i '<dashboard-name-or-theme>' ``` 2. Export dashboard and JSON: ```bash skills/grafana-platform-dashboard/scripts/grafanadashboard_roundtrip.sh export \ --context <ctx> \ --namespace <ns> \ --name <grafanadashboard-name> \ --out-dir /tmp/<workspace> ``` 3. Edit the JSON and validate all PromQL: ```bash skills/grafana-platform-dashboard/scripts/promql_scan_thanos.sh \ --context <ctx> \ --dashboard-json /tmp/<workspace>/<name>.json ``` 4. Apply live safely: ```bash skills/grafana-platform-dashboard/scripts/grafanadashboard_roundtrip.sh apply \ --context <ctx> \ --namespace <ns> \ --name <grafanadashboard-name> \ --json /tmp/<workspace>/<name>.json ``` ## Workflow ### 1) Lock Scope From Platform Contracts Use the platform contract in [platform-contract.md](references/platform-contract.md) before editing panels. 1. Keep L1 command view constrained to critical pre-tenant-impact signals. 2. Use gate-aligned components first (critical CO gate, nodes, MCP, core API/etcd/ingress). 3. Keep service-specific sections (Crossplane, Keycloak) below L1. ### 2) Enforce Information Architecture Use [layout-gui