Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate Statuspage for rusk and web wallet #1478

Open
Daksh14 opened this issue Feb 29, 2024 · 2 comments
Open

Integrate Statuspage for rusk and web wallet #1478

Daksh14 opened this issue Feb 29, 2024 · 2 comments
Labels
module:explorer Issues related to explorer module module:web-wallet Issues related to web-wallet module type:enhancement Issues concerning code or feature improvement (performance, refactoring, etc)

Comments

@Daksh14
Copy link
Contributor

Daksh14 commented Feb 29, 2024

Summary

💡 Add a clear and concise description of the reason why this needs to be worked on. Focus on the big picture rather than implementation details. What use case does it support? What is the expected outcome?

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

💡 Add clear and concise description of concrete solutions you've considered. Include possible drawbacks. Add diagrams, pictures, description, code-snippets, or anything else that might help solving the issue. Consider adding different implementation alternatives with tradeoffs.

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.

@HDauven HDauven added module:explorer Issues related to explorer module module:web-wallet Issues related to web-wallet module type:enhancement Issues concerning code or feature improvement (performance, refactoring, etc) labels Apr 9, 2024
@nortonandreev
Copy link
Contributor

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

@HDauven
Copy link
Member

HDauven commented May 27, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module:explorer Issues related to explorer module module:web-wallet Issues related to web-wallet module type:enhancement Issues concerning code or feature improvement (performance, refactoring, etc)
Projects
None yet
Development

No branches or pull requests

3 participants