Problem
The v2.5.0 estate rollup produces estate-rollup.json, estate-summary.html, and powerbi/estate-clusters.csv. The HTML is a basic table; there's no heatmap, no trend view, no drilldown. Multi-cluster operators need an actually-useful estate dashboard.
Goals
Upgrade estate outputs so a single file communicates the health of an entire estate and lets the reader drill in.
Scope
- Estate summary HTML redesign
- Cross-cluster heatmap (rows = clusters, columns = WAF pillars; color = score)
- Capacity heatmap (rows = clusters, columns = dimensions)
- Top-10 findings across the estate with affected cluster list
- Trend charts if historical
estate-rollup.json files are present
- Drill-down — clicking a cluster in the summary opens that cluster's executive-summary.html (file:// links into the per-cluster subfolders)
- Estate manifest schema — document
estate-rollup.json structure with a JSON Schema
- CSV expansion — add per-pillar columns, capacity columns, cost/AHB columns per cluster
- Estate SVG — a cross-cluster topology diagram showing all clusters, their sizes, and connectivity
- Estate PPTX — estate-level presentation deck alongside per-cluster decks
- Diff between estate runs — given two estate-rollup.json files, show cluster-level health delta
Research inputs
- VMware vRealize Operations multi-cluster summary views
- Datadog infrastructure host map
- Nutanix Prism Central multi-cluster dashboard
- Azure Arc estate view in the portal
Acceptance criteria
Problem
The v2.5.0 estate rollup produces
estate-rollup.json,estate-summary.html, andpowerbi/estate-clusters.csv. The HTML is a basic table; there's no heatmap, no trend view, no drilldown. Multi-cluster operators need an actually-useful estate dashboard.Goals
Upgrade estate outputs so a single file communicates the health of an entire estate and lets the reader drill in.
Scope
estate-rollup.jsonfiles are presentestate-rollup.jsonstructure with a JSON SchemaResearch inputs
Acceptance criteria
docs/samples/outputs/estate/