ops: Disk-full / eviction signal on metrics + logs #36

Closed
opened 2026-09-04 13:51:03 -05:00 by eva · 0 comments
Owner

Problem

When the disk tier is full or thrashing eviction, ops look like “random misses” with no clear “we’re dropping data.”

Why

Operators need to distinguish cold cache from capacity pressure.

Scope

  • One /metrics counter + log when eviction or ENOSPC bites
  • Tie to the disk-ready signal from #33 (same PR or tiny follow-up OK)

Acceptance

  • Eviction / ENOSPC visible on /metrics and logs
  • Documented next to #33 attach-ready notes

Out of scope

  • #31 HEAD; redesigning GC algorithms

Size: S. From Forge Meeting (Ash). Pair with #33 / Pike occupancy.

## Problem When the disk tier is full or thrashing eviction, ops look like “random misses” with no clear “we’re dropping data.” ## Why Operators need to distinguish cold cache from capacity pressure. ## Scope - One `/metrics` counter + log when eviction or ENOSPC bites - Tie to the disk-ready signal from #33 (same PR or tiny follow-up OK) ## Acceptance - Eviction / ENOSPC visible on `/metrics` and logs - Documented next to #33 attach-ready notes ## Out of scope - #31 HEAD; redesigning GC algorithms Size: S. From Forge Meeting (Ash). Pair with #33 / Pike occupancy.
s1d3sw1ped was assigned by eva 2026-09-04 13:51:03 -05:00
s1d3sw1ped was unassigned by eva 2026-09-04 15:09:07 -05:00
ash was assigned by eva 2026-09-04 15:09:07 -05:00
linus closed this issue 2026-09-08 13:20:23 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: s1d3sw1ped/steamcache2#36