Skip to content

feat(dashboard): expose additional drive metrics — available space, self-test history, performance #470

Closed

Description

@Starosdev

Feature Request

Environment

  • Affected: Both
  • Component: Backend / Frontend

Description

Umbrella issue tracking expansion of drive metrics surfaced in the dashboard and device detail view. Three metric categories are currently missing from the UI despite partial backend support:

1. Available Space

Drive capacity and free space are not shown anywhere in the UI. smartctl reports capacity; filesystem free space could be read from the host. Useful for monitoring drives approaching full.

2. Self-Test History

smartctl returns ata_smart_self_test_log with pass/fail history for short and extended self-tests. This data is parsed in collector/smart.go but not persisted or displayed. Showing recent self-test results on the device detail page would give users direct visibility into drive health checks.

3. Drive Performance Summary

Performance benchmark data (fio results) is collected by the performance collector and stored via /api/device/:wwn/performance, but there is no UI to browse or trend this data on the device detail page.


Technical Details

  • Self-test log parsed: webapp/backend/pkg/models/collector/smart.go:168
  • Performance API endpoint: GET /api/device/:wwn/performance
  • Available space: no current collection — needs new collector logic or OS-level query

Acceptance Criteria

  • Self-test history displayed on device detail page (pass/fail, date, type)
  • Performance benchmark history viewable on device detail page
  • Available space shown on device card and detail page (capacity + used + free)
  • All three metrics included in device detail API response
  • Mobile card layout updated to include new metrics

Activity

  1. Starosdev commented on Jul 17, 2026

    @Starosdev
    OwnerAuthor

    Status audit: current develop displays ATA self-test history and performance benchmarks on the detail page, and has a filesystem capacity panel with available, used, and total bytes. Remaining gap: per-drive available/free space on device cards and detail, plus any required API/mobile parity. Keeping open for residual scope.

  2. Starosdev commented on Oct 30, 2026

    @Starosdev
    OwnerAuthor

    Shipped in v1.78.0.

    Closing by hand because the closing keyword never fired: #1041 merged into develop, and GitHub only auto-closes from the default branch, while the promotion PR #1060 referenced this issue in prose rather than with a keyword. #1060's body now carries Closes #470 and the v1.78.0 notes link it.

    All three parts of this issue are in the release: self-test history and performance benchmark history on the device detail page shipped earlier, and per-drive available space shipped in #1041 with follow-ups #1055 and #1059. Verified against real hardware on a test instance: 14 of 18 device cards report free space, including every Unraid array disk and the NVMe cache drive.

    Per-drive figures need the filesystem collector enabled and the same COLLECTOR_HOST_ID on every collector; that collectors disagree on the empty default is tracked in #1046.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions