Repository navigation
Conversation
Two dashboards exist in CCI-MOC/oac-apps at 457b659: - MCO capacity and growth: one dashboard, rendered as a PersesDashboard and as a console ConfigMap with the same panels and queries. - Project overview: the GrafanaDashboard shipped with the per-project Grafana in user-projects. Each page uses the same sections: Question and audience, Tool and location, Data source, Metrics, Thresholds, Dependencies, Owner, Open points, See also. The Metrics table gives, per panel, the PromQL as in the repo, where the metric comes from, whether it needs the MCO allowlist, and why it is there. Where the reason is not recorded in oac-apps, the page says so and lists it as an open point. The dashboard strategy ADR is referenced as pending.
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.
Intent
Dashboards are built for the OAC clusters (Grafana, Perses, OpenShift Console Observe), today only in oac-apps (https://github.com/schwesig/OA_oac-apps, fork of CCI-MOC/oac-apps). The goal is to always know why a dashboard was created and why it is fed with which metrics:
"ich baue ja auch dashboards, ich wuerde gerne entweder ein ADR pro Dashboard oder ein ADT fuer mehrere Dashboards (Grafana, Perses, OpenSHift COnsole Ob serve) erstellen, damit man immer weiss, warum man was erstellt und mit diesen metriken etc gefuettert hat."
Agreed split ("ja passt, bisher nur in OAC-APPS"): one ADR for the dashboard strategy (which tool for which audience and purpose, data sources, dashboards as code, naming and ownership; referencing rather than repeating the existing per-project Grafana ADR in CCI-MOC#37 and the MCO allowlist ADR in CCI-MOC#36), plus one short document per dashboard in ops-docs docs/ (what question it answers and for whom, tool and repo location, data source, metrics with PromQL and why/where each metric comes from, thresholds, dependencies such as the MCO allowlist, owner, related ADRs). A separate ADR per dashboard only where a dashboard forces a real decision.
All work and PRs only on the fork schwesig/ops-docs; never on CCI-MOC.
What Changed
docs/2026-10-20-dashboard-mco-capacity/README.md. It documents the MCO capacity and growth dashboard, which has a PersesPersesDashboardrendering and a console ConfigMap rendering. The page covers the question it answers, who it is for, its data source (the hub's ownthanos-querier, not MCO's Grafana), each panel's PromQL with the metric's origin and why it is there, thresholds (none), dependencies, owner (not recorded) and open points. The open points include the pending[5m]rate-window fix in oac-apps#149 and the dashboard being rendered on clusters without MCO.docs/2026-10-20-dashboard-project-overview/README.md. It documents the per-project Grafanaproject-overviewdashboard with the same structure: tenancy datasource on port 9092, the CPU and memory PromQL and why the namespace is named in each query, dependencies, and open points such as panel choice and the fact that it is only on dev so far.457b659and say whether each dashboard needs the MCO allowlist (neither does). They reference the per-project Grafana ADR (adr: Separate project metrics with one Grafana per project on the tenancy port CCI-MOC/ops-docs#37) and the MCO allowlist ADR (adr: Collect central metrics using MultiClusterObservability allowlist keeping exclusion lists as a future change CCI-MOC/ops-docs#36) instead of repeating them. They also link toadrs/2026-09-04-dashboard-strategy/, marked Proposed. That ADR is not in this branch and is in review in a separate PR, so the link stays broken until that PR merges.🤖 Generated with Claude Code
Risk Assessment
✅ Low: The change only adds two docs pages that follow the repo's docs template and match the agreed split (the strategy ADR lives on a separate branch), and nothing executable is touched.
Testing
I built and served the ops-docs Eleventy site from this branch and browsed it over HTTP. Frontmatter validation passes. Both dashboard pages render fully and appear in the docs index. Each page covers question and audience, tool and location, data source, metrics with PromQL, thresholds, dependencies, owner, open points and related ADRs. Angle-bracket placeholders render as visible text, and the two pages link to each other correctly. The strategy-ADR link is a 404 on this branch, which you already accepted. There are no screenshots: the chrome-devtools-axi bridge never started (BRIDGE_NOT_READY, the Chrome target exited), so the evidence is the rendered HTML pages saved with their CSS. The temporary site, the HTTP server and node_modules were removed afterwards.
npm run validate-frontmatterexit 0Evidence: Rendered MCO capacity dashboard page (built by Eleventy)
Evidence: Rendered Project overview dashboard page (built by Eleventy)
Evidence: Rendered Technical Documentation index listing both pages
Evidence: Rendered page headings
Pipeline
Updates from git push no-mistakes
✅ **intent** - passed
✅ No issues found.
✅ **Rebase** - passed
✅ No issues found.
docs/2026-10-20-dashboard-mco-capacity/README.md:9- Both dashboard pages refer to the strategy ADR as the placeholderadrs/<date>-dashboard-strategyand call it "pending". The sibling branch fm/ops-docs-dashboard-adr already adds it asadrs/2026-09-04-dashboard-strategy. Once that ADR merges (or if this branch lands after it), replace the placeholder with a real relative link,../../adrs/2026-09-04-dashboard-strategy/, so readers can follow it. The same placeholder appears at docs/2026-10-20-dashboard-mco-capacity/README.md:9 and :150, docs/2026-10-20-dashboard-mco-capacity/README.md:141 (open point 4), and docs/2026-10-20-dashboard-project-overview/README.md:9, :140 (open point 3) and :151.🔧 Fix applied.
2 infos still open:
docs/2026-10-20-dashboard-mco-capacity/README.md:9- Both dashboard pages refer to the strategy ADR as the placeholderadrs/<date>-dashboard-strategyand call it "pending". The sibling branch fm/ops-docs-dashboard-adr already adds it asadrs/2026-09-04-dashboard-strategy. Once that ADR merges (or if this branch lands after it), replace the placeholder with a real relative link,../../adrs/2026-09-04-dashboard-strategy/, so readers can follow it. The same placeholder appears at docs/2026-10-20-dashboard-mco-capacity/README.md:9 and :150, docs/2026-10-20-dashboard-mco-capacity/README.md:141 (open point 4), and docs/2026-10-20-dashboard-project-overview/README.md:9, :140 (open point 3) and :151.docs/2026-10-20-dashboard-mco-capacity/README.md:9- The round-1 fix links to ../../adrs/2026-09-04-dashboard-strategy/. That path exists only on the sibling branch fm/ops-docs-dashboard-adr (adrs/2026-09-04-dashboard-strategy/README.md, Status: Proposed), so the link is a 404 on this branch until the ADR PR merges. The user chose this link explicitly in round 1. Nothing in pre-commit checks links, so CI will not fail on it. The point is merge order: merge the ADR PR first, or accept the broken links for a while. The same link appears at docs/2026-10-20-dashboard-mco-capacity/README.md:9 and :161, and at docs/2026-10-20-dashboard-project-overview/README.md:9 and :155.npx chrome-devtools-mcp@latest --helpand stop any stale bridge), then re-run.npm run validate-frontmatterexit 0npm ci(in the worktree; node_modules removed afterwards)npm run validate-frontmatter: exit 0npx eleventy --output=/tmp/nm-site-01M5: built 12 files, including both dashboard pagesServed the built site withpython3 -m http.server 8731and fetched both dashboard pages with curl (HTTP 200) and the strategy ADR link (HTTP 404, as expected)Checked the rendered HTML: both pages are listed in docs/index.html, the section headings are complete, the PromQL table rows are there,<name>-style placeholders are shown as escaped text inside code, and no{{/{%reached the pageChecked internal links: the two pages link to each other (both resolve) and both link to ../../adrs/2026-09-04-dashboard-strategy/ (404 on this branch)Triedchrome-devtools-axi open/screenshotfor screenshots: the bridge failed every time (BRIDGE_NOT_READY / CDP target gone)✅ **Document** - passed
✅ No issues found.
✅ **Lint** - passed
✅ No issues found.
✅ **Push** - passed
✅ No issues found.