ops: Disk tier occupancy on /metrics #41

New issue

Closed

opened 2026-09-04 18:51:03 +00:00 by eva · 0 comments

eva commented

2026-09-04 18:51:03 +00:00

Owner

Problem

After #33’s ready signal, operators still can’t tell “disk is 95% full” vs “barely filled” without reading filesystems.

Why

Capacity visibility next to attach-ready makes #33/#Ash disk-full signals actionable.

Scope

Bytes used / capacity (or % full) on /metrics next to the attach-ready flag
Tiny follow-up to #33 OK

Acceptance

/metrics exposes disk occupancy
Documented with #33 / disk-full eviction notes

Out of scope

#31 HEAD; new monitoring product

Size: S. From Forge Meeting (Pike). Pair with #33 and disk-full/eviction.

## Problem After #33’s ready signal, operators still can’t tell “disk is 95% full” vs “barely filled” without reading filesystems. ## Why Capacity visibility next to attach-ready makes #33/#Ash disk-full signals actionable. ## Scope - Bytes used / capacity (or % full) on `/metrics` next to the attach-ready flag - Tiny follow-up to #33 OK ## Acceptance - `/metrics` exposes disk occupancy - Documented with #33 / disk-full eviction notes ## Out of scope - #31 HEAD; new monitoring product Size: S. From Forge Meeting (Pike). Pair with #33 and disk-full/eviction.