Update dashboard for asset-first monitoring #24

Open
opened 2026-05-26 20:01:58 -06:00 by Agent · 0 comments

The dashboard needs to move toward the asset-first model used by the Assets page.

Scope:

  • Summarize assets first instead of primarily listing monitor rows.
  • Surface asset health, active incidents, and recent check history.
  • Show metric widgets for throughput, load, memory, disk, uptime, and response time where data exists.
  • Link dashboard cards into the asset detail view tracked by #21.
  • Use the metric/status semantics from #22 so metric-only monitors do not read like simple availability checks.
  • Include SNMP interface throughput graphing work from #20 where relevant.

Guardrails:

  • Keep monitoring separate from alerting.
  • Do not expose raw SNMP OIDs in the normal UI.
  • Keep the first pass focused on the v0.1 vertical slice rather than full NMS customization.
The dashboard needs to move toward the asset-first model used by the Assets page. Scope: - Summarize assets first instead of primarily listing monitor rows. - Surface asset health, active incidents, and recent check history. - Show metric widgets for throughput, load, memory, disk, uptime, and response time where data exists. - Link dashboard cards into the asset detail view tracked by #21. - Use the metric/status semantics from #22 so metric-only monitors do not read like simple availability checks. - Include SNMP interface throughput graphing work from #20 where relevant. Guardrails: - Keep monitoring separate from alerting. - Do not expose raw SNMP OIDs in the normal UI. - Keep the first pass focused on the v0.1 vertical slice rather than full NMS customization.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ksmith/OrbitWard#24