feat: implement /api/logs reverse proxy with per-endpoint circuit bre… - #1007
Merged
greatest0fallt1me merged 4 commits intoJul 29, 2026
Conversation
|
@TechBroAfrica Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Author
|
@greatest0fallt1me kindly review, conflict resolve. |
Contributor
|
CI green, LGTM ✨ merged. |
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
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.
closes #944
Here is a draft for your PR message. You can copy and paste this directly into your GitHub pull request:
Title: feat: add per-endpoint circuit breaker for downstream calls on /api/logs
Description:
This PR introduces a dedicated proxy router for downstream logging services with per-endpoint circuit breaking, successfully fulfilling the requirements for the GrantFox FWC26 campaign.
The
/api/logsendpoint acts as a resilient proxy that fast-fails with an HTTP503 Service Unavailableif the downstream service experiences an outage.🚀 Key Changes
src/routes/logs.ts: Added a new reverse proxy router matchingALL /api/logs/:endpoint(*)?. It tracks downstream failures dynamically per-endpoint using theBreakerRegistry.src/lib/circuitBreaker.ts: Added an optionalonOpenErrorcallback to theCircuitBreakerConfig. This safely enables thelogsroute to fast-fail with a customizableServiceUnavailableError(503) without mutating the global502 Bad Gatewaybehaviors currently expected for Horizon endpoints.src/index.ts: Registered the newlogsRoutercentrally.src/routes/logs.test.ts: Implemented a comprehensive test suite that verifies the circuit breaker correctly triggers the503 Service Unavailableresponse after reaching the failure threshold (5 attempts).docs/api-logs.md: Created new documentation explicitly covering the expected API interface, parameters, and its fast-fail circuit breaker behavior.✅ Testing & Validation
npm test -- src/routes/logs.test.ts).anytype violations introduced.