Shed decisions are not recorded server-side
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- prometheus, rust
- Domain
- observability
Research direction
Start by finding where grid_route_decisions_total is defined and incremented, then trace how the gateway handles 429 responses. Add a distinct shed reason to the existing counter and run the relevant metrics tests; done means shed decisions are recorded separately from routed and fallback decisions.
Written by the indexing model from the issue text.
Description
A shed decision is not recorded server-side.
grid_route_decisions_total carries routed and fallback only. When the gateway answers 429 the decision is visible to the client and nowhere else, so there is no server-side rate, no per-replica attribution, and no way to distinguish a grid shed from a rate limiter in front of the grid.
Found while trying to measure whether two gateway replicas diverge on the shed latch under load. That measurement is not possible with the metrics that ship today. It also makes load tests ambiguous: in one run 3751 of 8000 requests answered 429 while the gateway recorded 3522 routed decisions, and establishing those 429s came from upstream rather than the grid took three separate lines of evidence.
Proposed: record a shed on the existing counter, most likely as a third reason value.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 24
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 138
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from praxis-proxy/grid
-
bug priority/high triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
praxis-proxy/grid#412 ·
Maintainers usually reply within 1 day
-
docs(gateway): memory sizing for prefix affinity capacityPossibly taken @valeriiashapoval claimed this 4 days ago. Opengood first issue priority/low triage/accepted
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
praxis-proxy/grid#406 · 1 assignee ·
Maintainers usually reply within 1 day
-
priority/low triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
praxis-proxy/grid#200 ·
Maintainers usually reply within 1 day
-
triage/needs-triage
Difficulty 5/5 Over a week Newbie friendliness 35/100
praxis-proxy/grid#455 · 3 comments ·
Maintainers usually reply within 1 day
-
triage/needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 68/100
praxis-proxy/grid#454 ·
Maintainers usually reply within 1 day
All issues in praxis-proxy/grid
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
area/desktop-shell P1-high
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
yantrikos/yantrik-os#998 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
warpdotdev/warp#16662 ·
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
crmne/spotifast#1105 · 1 comment · 1 reaction ·
Maintainers usually reply within 2 days