Hubs and Dashboards
Dashboard Hub uses hubs as the top-level workspace. Dashboards, containers, and widgets live inside a hub.
Hierarchy
Hub
└── Dashboard
└── Container
└── Widget
| Level | Responsibility |
|---|---|
| Hub | Domain or team workspace (Observability, Finance, Default Hub, …) |
| Dashboard | Named view with filter type, icon, tags, and publish state |
| Container | Layout section / template block that groups widgets |
| Widget | Visualization or control bound to a data source |
Hubs
Hub records typically include:
| Field | Purpose |
|---|---|
| name / description | Operator-facing identity |
| icon | Visual cue on the hubs grid |
| order | Sort position among hubs |
| defaultHub | Marks the primary authoring hub when set |
| metadata | Optional domain/category tags |
Default Hub vs domain hubs
| Hub style | Typical use |
|---|---|
| Default Hub | Primary authoring space where users create dashboards and widgets from scratch; mock/direct data is a baseline source |
| Domain hubs (Observability, Finance, Security, …) | Curated or specialized dashboards for a function; manage rights may be narrower than Default Hub |
Exact feature grants differ by hub — see Publishing and Permissions.
Dashboards
When creating a dashboard you commonly set:
| Field | Purpose |
|---|---|
| name | Title in lists and breadcrumbs |
| description | Context for other editors |
| hubId | Parent hub (required) |
| icon | Optional visual marker |
| filterType | MONTH, TIME, or NONE for dashboard filter chrome |
| tags | Discovery and grouping aids |
Dashboards can be unpublished while under construction, then published to selected users.
Containers
Containers structure the dashboard body. They support:
- Adding, updating, and deleting container blocks
- Rearranging container order/position
- Hosting one or more widgets
- Using container templates (for example executive or monitoring layouts) when seeded by the service
Nested container widgets can create richer compositions when the Nested Container widget type is available.
Personal preference layouts
Dashboard Hub distinguishes authored layout from personal preference layout:
| Layout | Who changes it | Purpose |
|---|---|---|
| Author / published structure | Users with manage rights | Canonical dashboard definition |
| Preference layout | Viewers with rearrange grants | Personal arrangement of containers/widgets without rewriting the shared definition |
This lets operators tune density for their work while publishers keep a stable shared view.
Authoring tips
- Keep one hub per audience or domain so publish scopes stay clear.
- Use tags and clear dashboard names before the inventory grows.
- Prefer container templates for recurring executive or monitoring layouts.
- Validate with mock data, then swap to live sources.
- Publish only when widgets degrade gracefully on empty or error states.