Public status page + incident communication - #1066
Open
Enchanterme wants to merge 1 commit into
Open
Conversation
|
@Enchanterme 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! 🚀 |
Contributor
|
@Enchanterme, please resolve conflicts |
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
2 participants
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.
I've successfully implemented the status page system for your platform. Here's what was completed:
Implementation Summary
Backend (Node.js/Express)
Created database migration 035_status_page.js with tables for incidents, maintenance, and subscribers
Built sqliteStatusRepository.js DAL for all status page operations
Updated status.js routes to use database persistence with proper health checks for API, RPC, Indexer, and Contracts
Integrated routes into main server with dependency injection for eventIndexer and rpcPool
Frontend (React)
Created StatusPage.jsx with real-time component status display
Shows active incidents with full lifecycle and updates
Displays scheduled maintenance windows
Email subscription form for status notifications
Auto-refreshes every 30 seconds
Added route at /status
Testing
Created comprehensive simulation test status-simulation.test.js (9 tests, all passing)
Verified end-to-end functionality via API calls:
Component health monitoring (RPC latency: 0-18ms)
Incident creation and lifecycle (investigating → identified → resolved)
Component status changes based on incident impact
Scheduled maintenance creation and display
Email subscription system
Closes #818
Closes #966
Closes #916
Closes #946