Dashboard Guide
A tour of the dashboard's main pages. Every page shares the same header (telemetry freshness, last update time, system count, open incidents) and the same facility-scoped data.
Your first daily check
- Confirm the organization/facility and last update time. Delayed, stale, or missing telemetry is not a healthy reading.
- Review Fleet’s attention items and open an affected storage system. Compare playback, drive health, host network, capacity, and maintenance evidence.
- Open the related incident to review its evidence and timeline. Assign responsibility through acknowledgment, add investigation notes, and verify recovery after any action.
The sandbox uses simulated data. Its scenarios demonstrate workflows, not your facility’s health or measured product performance.
1.Main Pages
| Page | Route | Purpose |
|---|---|---|
| Fleet | /dashboard | Facility-wide landing page: editorial readiness summary, items needing attention, upcoming risks, the storage systems table, recent incidents, throughput, and capacity — plus the empty-fleet pairing CTA for a facility with no nodes yet. |
| Storage | /storage | One row per storage system, filterable by platform, health, Observer presence, capacity risk, and open incidents. Columns cover agent/Observer state, pool health, playback latency, capacity, maintenance, and problem drives. |
| Incidents | /incidents | Full incident list across open / acknowledged / resolved / all, filterable by severity, node, diagnostic type, and time window. |
| Maintenance | /maintenance | Reported scrub/resilver/parity activity, projected completions, and operating-hour collisions. Future host schedules are not collected; completed history depends on reported timestamps. |
| Capacity | /capacity | Every pool ranked by shortest runway to its capacity warning threshold, with 7-day and 14-day at-risk counts surfaced up front. |
| Chargeback | /chargeback | Dataset-to-project allocation and statement exports on eligible plans. All roles can view; Billing Admins and Organization Admins can manage allocations. |
| Security Posture | /security-posture | Technical deployment-control evaluation with per-node evidence, history, and role-controlled exports. It is not an external compliance certification. |
| Settings | /settings | The eight configuration sections — see the dedicated Settings reference. |
2.Per-Node Investigation
Clicking any storage system opens a node investigation view with tabbed sections:
overview, playback, network, capacity, maintenance, topology, drives, incidents — reachable either as a full page (/storage/<node>?tab=<tab>) or as an inline drawer opened from the Fleet page without leaving the facility overview.
3.Search
Global search (facility-scoped) covers nodes, pools, datasets, drives, enclosures, incidents, and — where configured — production suites and projects, so an engineer can jump directly to the object they're investigating instead of navigating through each page.
4.Notifications
The header bell shows recent notifications with a dedicated Notifications page for the full history (up to 200 most recent), with per-user seen state. Marking a notification seen does not acknowledge or resolve its incident, and does not prove external alert delivery.
See also