ops: Disk tier occupancy on /metrics #53
Reference in New Issue
Block a user
Delete Branch "ops/disk-tier-occupancy-metrics"
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?
Why
After disk-tier attach-ready (#33 / #45) and capacity-pressure (#46), operators still could not tell "disk is 95% full" vs "barely filled" from
/metricsalone.What
memory_cache_capacity/disk_cache_capacitygauges (configured bytes; disk capacity 0 when no disk)disk_cache_full_ratio(size/capacity in [0,1]) next to existing size gauges anddisk_tier_readyGetMetrics()viaCapacity()(safe during pending attach; still skipdisk.Size()while pending)Test
go test ./steamcache/metrics ./steamcache -count=1Rollback
git revertthe merge commit. No DB / schema.Implements: #41
Do not merge yourself — leave merge to reviewer.
LGTM — occupancy gauges match #41; Capacity() safe during pending attach; no service-label collision; CI green (check-and-test + vulncheck). Merging FF.