Availability Issues
Trigger alerts when RPC endpoints stop responding or repeated requests fail.
RPC Alerts
RPC Alert Scenarios
Turn changes in RPC availability, latency, error rates and response quality into alerts that teams can receive, pause and acknowledge.
Latency Increase
Treat sustained latency increases as medium or high-priority alert scenarios.
Error Spikes
Help teams review service status when error rates rise in clusters.
Acknowledgement
Confirm the alert in the app and keep the status in alert history.
How RPC Alerts Work
Organize RPC endpoint status, response quality and error signals into an actionable alert workflow.
RPC Alerts
RPC Alert Scenarios
Turn RPC availability, latency, errors and response quality changes into alert scenarios.
- Endpoint availability checks
- Response latency rules
- Request error spike alerts
- Alert assistant integration
Alert Scenarios
Different teams can set different alert priorities around RPC status changes.
Wallet Infrastructure
Wallet services rely on RPC availability and need timely alerts during outages.
DApp Backends
Backend teams can quickly review impact when RPC latency increases or requests fail.
Trading Systems
Trigger team alerts when transaction submissions or status queries become abnormal.
Node Operations
Enter the handling workflow when node or upstream service states change.
Platform Teams
Unify severity levels and records across multi-RPC setups.
Alert Workflow
Define Scenario
Identify RPC endpoints and alert dimensions to discuss.
Set Severity
Plan latency, error rate and availability alert thresholds.
Configure Alerts
Route warning and critical events to the alert assistant.
Review History
Acknowledge alerts and review recent historical alert records.
Alert Sources & Notification
RPC issues can become one of the alert sources, with notification methods configured based on team needs.
This format illustrates the event structure. Actual fields and interfaces should follow the official documentation.
Alert State
alert-state.json
{
"alert_type": "critical",
"severity": "high",
"status": "active",
"action": "acknowledge_required"
}