Skip to content

output: revisit estate rollup outputs — cross-cluster visual summary, heatmaps, trend tracking #286

Description

@kristopherjturner

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

  1. 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
  2. Drill-down — clicking a cluster in the summary opens that cluster's executive-summary.html (file:// links into the per-cluster subfolders)
  3. Estate manifest schema — document estate-rollup.json structure with a JSON Schema
  4. CSV expansion — add per-pillar columns, capacity columns, cost/AHB columns per cluster
  5. Estate SVG — a cross-cluster topology diagram showing all clusters, their sizes, and connectivity
  6. Estate PPTX — estate-level presentation deck alongside per-cluster decks
  7. 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

  • Estate heatmap in HTML summary
  • Drilldown links from estate to per-cluster reports
  • Estate JSON Schema committed
  • Estate PPTX deck
  • Estate SVG topology diagram
  • Sample outputs under docs/samples/outputs/estate/

Metadata

Metadata

Assignees

No one assigned

    Labels

    ado-trackedIssue has a linked ADO work itemenhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions