dashboard-v2
The dashboard-v2 aggregation node validates $heat-dataservice, merges realm hints into layoutConfiguration, and creates a Next dimension for ui/dashboard.
When to use it
Use for integrator-owned Next dashboards when your graph already produces canonical (or normalizable) $heat-dataservice and a v2 layout with components.rows.
Limitations
- Input must include
$heat-dataserviceanddashboard_users(snake_case). Flatchannelsis accepted and normalized to nestedrealmsbefore storage. - 50-realm soft cap: default logs a warning; set
failOnRealmCountExceeded: true to fail the node. - Does not target
ui/legacy; use dashboard for v1.
Configuration (required)
| Property | Description |
|---|---|
dataSourceName | Data source for stored payload |
layoutConfiguration | Object with components.rows (v2 layout schema) |
dashboardName | Display name |
Optional: dashboardVersion (Next default), failOnRealmCountExceeded, scenario auto-create fields (same pattern as v1).
Authoritative contract
Channel shapes, realm semantics, layout merging, and examples: dashboard-v2 upstream contract.
UI consumption: Next data service.