Description
Build a protocol health monitoring dashboard that provides real-time visibility into system metrics, contract performance, and operational health. This goes beyond the public /stats page — it's an internal operations view for maintainers to monitor the protocol's live state, detect anomalies, and respond to issues.
Current state
The public /stats page shows aggregate totals. There is no operational monitoring for contract state, transaction success rates, gas consumption, or error patterns.
Proposed implementation
Metrics Collection
- Transaction success/failure rates per contract function
- Gas consumption trends and outliers
- Average confirmation times by network congestion
- Error code distribution (categorized by severity)
Contract State Monitoring
- Active invoice count and status distribution
- Insurance pool utilization ratio
- Position token supply and holder count
- Repayment rate and overdue ratio (time-series)
Alerting
- Threshold-based alerts (e.g., overdue rate > 15%)
- Anomaly detection on transaction patterns
- Contract pause state indicator
- Admin action audit log viewer
Dashboard UI
- Real-time charts using Recharts or similar
- Time-range selector (1h, 24h, 7d, 30d)
- Drill-down from summary to individual transactions
- Export metrics as CSV for external analysis
Data Pipeline
- Supabase tables for metrics aggregation
- Scheduled Edge Functions or GitHub Actions for data collection
- Soroban RPC event subscription for real-time ingestion
- Retention policy for historical data
Acceptance criteria
Dependencies
- Benefits from event indexing system (Task 13)
- Requires admin authentication gate
Complexity
High — Real-time data pipeline, metrics aggregation, charting library integration, alerting system, and admin-only access control.
Description
Build a protocol health monitoring dashboard that provides real-time visibility into system metrics, contract performance, and operational health. This goes beyond the public /stats page — it's an internal operations view for maintainers to monitor the protocol's live state, detect anomalies, and respond to issues.
Current state
The public /stats page shows aggregate totals. There is no operational monitoring for contract state, transaction success rates, gas consumption, or error patterns.
Proposed implementation
Metrics Collection
Contract State Monitoring
Alerting
Dashboard UI
Data Pipeline
Acceptance criteria
Dependencies
Complexity
High — Real-time data pipeline, metrics aggregation, charting library integration, alerting system, and admin-only access control.