Proposal for Monitoring of public RPC/WSS Endpoints & Node Database Analytics

Dear community,

I present to you a proposal which aims to develop a technical solution to:

Monitor and report on the uptime, performance and integrity of public WSS (RPC) relay-chain endpoints. The data could be used to guide funding of said services, to encourage a service standard or to provide existing providers with a second take on key metrics from a third-party.
Monitor and trend database growth rates for twenty-four database configurations. This is something that I started and self-funded > 16 months ago. Upon launch it gained interest by technical parties and is now referenced within the Polkadot Wiki. I would like to expand on the project to include growth charts and offer a wider range of database configurations. Further to this, I intend to monitor the restoration times of some of the more popular database configurations.

Additional: Providing that the original scope is met, I'll consider monitoring of database bloat, trend average RAM or CPU usage as well as monitor availability and integrity of bootnodes.

Both major items are not found within any existing public resources and are in my opinion well aligned to Kusama's experimental nature. Full details including budget details can be found in the proposal document. This document was circulated to members of the 1KV/IBP for a week and was open for public discussion for > 2 weeks.

Disclosure: As it relates to WSS monitoring, I am presently employed by LuckyFriday which as of last week is now listed as a public RPC provider. I also share good professional relationships with most of the RPC providers. The proposed solution is open sourced such that anyone can operate in-tandem and compare/challenge results. Once up and running these `audits` will be operated and presented without any human intervention.

Kind Regards,

Will | Paradox

A proposal to create tools for checking how well public WSS (RPC) relay-chain endpoints are working.
The tools will track uptime, performance, and integrity to help improve services.
Another part of the project will monitor how fast databases grow and how long it takes to restore them.
The project will also include growth charts and more database options.
If successful, it might also track database bloat, RAM/CPU usage, and bootnode availability.
The proposal is open for public review and has been shared with experts.
The tools will be open-source, so anyone can use or check the results.
The project aligns with Kusama's experimental nature and aims to improve transparency.

Source

Dear community,

I present to you a proposal which aims to develop a technical solution to:

Monitor and report on the uptime, performance and integrity of public WSS (RPC) relay-chain endpoints. The data could be used to guide funding of said services, to encourage a service standard or to provide existing providers with a second take on key metrics from a third-party.
Monitor and trend database growth rates for twenty-four database configurations. This is something that I started and self-funded > 16 months ago. Upon launch it gained interest by technical parties and is now referenced within the Polkadot Wiki. I would like to expand on the project to include growth charts and offer a wider range of database configurations. Further to this, I intend to monitor the restoration times of some of the more popular database configurations.

Additional: Providing that the original scope is met, I'll consider monitoring of database bloat, trend average RAM or CPU usage as well as monitor availability and integrity of bootnodes.

Both major items are not found within any existing public resources and are in my opinion well aligned to Kusama's experimental nature. Full details including budget details can be found in the proposal document. This document was circulated to members of the 1KV/IBP for a week and was open for public discussion for > 2 weeks.

Disclosure: As it relates to WSS monitoring, I am presently employed by LuckyFriday which as of last week is now listed as a public RPC provider. I also share good professional relationships with most of the RPC providers. The proposed solution is open sourced such that anyone can operate in-tandem and compare/challenge results. Once up and running these `audits` will be operated and presented without any human intervention.

Kind Regards,

Will | Paradox