feat(#504): add provider failover incident history#572
Open
coredevdave-cmd wants to merge 1 commit into
Open
Conversation
- Add failoverIncidentHistoryService with in-memory store for recording, resolving, and querying failover incidents (stale data, outage, degraded) - Add GET/POST /api/transparency/failover-history and POST /api/transparency/failover-history/:protocolId/resolve endpoints - Render incident history panel in TransparencyDashboard with active/ recovered status, trigger type, duration, and reasons - Add server-side tests for incident creation, recovery, and empty history - Add client-side tests for the incident history panel rendering
|
@coredevdave-cmd is attempting to deploy a commit to the Edeh Victor's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@coredevdave-cmd 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! 🚀 |
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.
closes #504
Summary
Implements issue #504: Provider Failover Incident History.
Changes
Server
server/src/services/failoverIncidentHistoryService.ts— in-memory store for failover incidents withrecordIncident(),resolveIncident(), andgetHistory(); auto-classifies trigger type (stale_data / outage / degraded) from reasonsserver/src/routes/transparency.ts— three new endpoints:GET /api/transparency/failover-history— returns incident list, newest first; optional?protocolIdfilterPOST /api/transparency/failover-history— record a new incidentPOST /api/transparency/failover-history/:protocolId/resolve— mark open incident as resolved, setsrecoveredAtanddurationMsClient
client/src/pages/transparency/TransparencyDashboard.tsx— new "Provider Failover Incident History" panel showing active/recovered status, trigger type, outage duration, and reasonsTests
server/src/services/__tests__/failoverIncidentHistoryService.test.ts— covers incident creation, recovery, empty history, and filteringclient/src/pages/transparency/TransparencyDashboard.test.tsx— covers empty state, active incident, and recovered incident with durationAcceptance Criteria