s1d3sw1ped/steamcache2
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 32 Wiki Activity

ops: Widen validate-check for upstream/write/rate failures #34

New Issue
Closed
opened 2026-09-04 13:24:47 -05:00 by eva · 0 comments
eva commented 2026-09-04 13:24:47 -05:00
Owner
Copy Link
Copy Source

Problem

#29 landed "is it caching?" via hit/miss in make validate-check. Metrics already expose upstream_errors / cache_write_failures / rate_limited, but the Quick check ignores them — so a hot failure path can look "fine" if hits exist.

Why

One glance should answer: caching, and the upstream pipe isn't on fire.

Scope

  • Highlight those fields in make validate-check output
  • One README line under Quick check
  • Same endpoints; no second metrics stack

Acceptance

  • make validate-check surfaces upstream errors, write failures, and rate limits alongside hit/miss
  • README Quick check mentions them
  • No new monitoring product

Out of scope

  • #31 HTTP HEAD
  • New metrics endpoints

From Forge Meeting (Linus ops list; Justin asked these filed).

## Problem #29 landed "is it caching?" via hit/miss in `make validate-check`. Metrics already expose `upstream_errors` / `cache_write_failures` / `rate_limited`, but the Quick check ignores them — so a hot failure path can look "fine" if hits exist. ## Why One glance should answer: caching, and the upstream pipe isn't on fire. ## Scope - Highlight those fields in `make validate-check` output - One README line under Quick check - Same endpoints; no second metrics stack ## Acceptance - `make validate-check` surfaces upstream errors, write failures, and rate limits alongside hit/miss - README Quick check mentions them - No new monitoring product ## Out of scope - #31 HTTP HEAD - New metrics endpoints From Forge Meeting (Linus ops list; Justin asked these filed).
s1d3sw1ped was assigned by eva 2026-09-04 13:24:47 -05:00
s1d3sw1ped was unassigned by eva 2026-09-07 09:54:15 -05:00
pike was assigned by eva 2026-09-07 09:54:15 -05:00
linus closed this issue 2026-09-07 14:53:37 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 draft
Draft for review — do not merge without Eva review
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ash blake eva linus moss pike s1d3sw1ped
No Assignees pike
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: s1d3sw1ped/steamcache2#34
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?