feat(relay): log non-429/403 upstream errors to KV for debugging#23
Open
iceteaSA wants to merge 1 commit into
Open
feat(relay): log non-429/403 upstream errors to KV for debugging#23iceteaSA wants to merge 1 commit into
iceteaSA wants to merge 1 commit into
Conversation
Adds logUpstreamError() to the worker script that writes error details to KV with 7-day TTL when the upstream Anthropic API returns 4xx/5xx (excluding 429 and 403 which are expected during normal operation). Logs include: status, headers, response body preview, transport mode, and affinity. Helps diagnose production issues without needing live Worker tail access.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
logUpstreamError()to the relay worker script. When the upstream Anthropic API returns 4xx/5xx (excluding 429 and 403, which are expected during normal rate-limiting), the error details are written to theRELAY_STATEKV namespace with a 7-day TTL.What's logged
Where it's called
Why
Debugging production relay issues currently requires live
wrangler tailaccess. This provides a persistent, queryable error log via KV that survives disconnects and can be inspected hours/days later.429 and 403 are excluded because they're normal rate-limit and auth responses that would flood the log.
Testing
All 214 tests pass. The logging is fire-and-forget via
ctx.waitUntil— no impact on response latency.