hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Add cached storage metrics refresh for backup data dashboards #98

New Issue
Open
opened 2026-06-08 22:40:15 +02:00 by parkel · 0 comments
parkel commented 2026-06-08 22:40:15 +02:00
Owner
Copy Link

Design and implement a durable storage metrics model so dashboard storage data, host backup data, storage runway, and related observability views are based on cached measurements rather than request-time scans. Measurements may be refreshed periodically by the worker/scheduler, and admins should have a way to request a manual refresh when needed.

Acceptance criteria:

  • Define which values are stored per snapshot, per host, and globally: allocated size, apparent size, unique/non-hardlinked estimates, measurement status, measured_at, source, and errors.
  • Add a safe periodic refresh path outside web requests, with bounds/timeouts or chunking for large targets.
  • Add a staff-only manual refresh action or queue trigger for stale/missing metrics.
  • Dashboard and host pages clearly show freshness/unknown states.
  • Storage runway calculations use explicit cached capacity/growth data and document assumptions.
  • Split implementation into smaller issues if the design grows beyond one PR.
Design and implement a durable storage metrics model so dashboard storage data, host backup data, storage runway, and related observability views are based on cached measurements rather than request-time scans. Measurements may be refreshed periodically by the worker/scheduler, and admins should have a way to request a manual refresh when needed. Acceptance criteria: - Define which values are stored per snapshot, per host, and globally: allocated size, apparent size, unique/non-hardlinked estimates, measurement status, measured_at, source, and errors. - Add a safe periodic refresh path outside web requests, with bounds/timeouts or chunking for large targets. - Add a staff-only manual refresh action or queue trigger for stale/missing metrics. - Dashboard and host pages clearly show freshness/unknown states. - Storage runway calculations use explicit cached capacity/growth data and document assumptions. - Split implementation into smaller issues if the design grows beyond one PR.
parkel added this to the 1.4 milestone 2026-06-08 22:40:15 +02:00
parkel added the area: observabilityfeature labels 2026-06-08 22:40:15 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label area: observability feature
Milestone
No items
No Milestone 1.4
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#98
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?