Open Daksh14 opened 7 months ago
To implement a status page effectively, we need to first identify which components are critical for users to monitor and which are less obvious. For instance, issues like the Wallet or Explorer websites being inaccessible are evident and might not require detailed status updates on a dedicated page.
However, providing an overall status of the network and the status of APIs would be valuable.
Before we proceed, we should consider integrating this with the Explorer project since users frequently visit the Explorer for network insights. It’s essential to determine the types of network and API status data we can realistically collect and display.
Overall, a status page would enhance transparency, provide proactive communication to users, and offer operational insights for developers and administrators. Let’s discuss the key metrics and components we want to monitor and explore potential tools for integrating status monitoring with our existing infrastructure.
cc: @Daksh14 @HDauven
The Solana status page looks at a cluster of operated nodes or known IPs, and pings them frequently.
We could ask a node, through its API or otherwise, to ping local nodes to see if they're still active, but if we want something similar to what Solana uses I don't see this being something we should implement in either the web-wallet or explorer in their current form.
But I do agree that it would be nice for the explorer or web-wallet to inform if the connected node is active.
Summary
Have a status page like Solana does at https://status.solana.com/ (even better -> https://incident.io/status-pages)
Or we could self host one on a independent server https://github.com/louislam/uptime-kuma
Possible solution design or implementation
We could send a curl request to the node.dusk.network topic: gql but we should have something that tells if specific things about the node, if its producing blocks or not, gas fees and how many transactions waiting to get accepted in mempool, consensus metrics, etc.