Additional checks

[kukabi]

• Votes and conviction checks on both Polkadot and Kusama.
• Genesis block and some random block retrieval in the range 0 < block <= chain tip checks for archive nodes.
• Boot node checks - not sure how it would work since boot nodes don't typically expose RPC ports.

[dcolley]

@paulormart is the alerts checking for genesis block or random early block?
checkBootnode is a capbility of the worker in 0.2.0 / develop.

[paulormart]

is the alerts checking for genesis block or random early block?

No. This is currently not being checked, i can look at it.

[paulormart]

Further check that needs implementation:

• Verify if node is in healthy state and not syncing

[dcolley]

we should have a worker for this - e.g. checkHistory
then the alert bot can run rules based on the worker name.

[paulormart]

Current checks and alerts implementation:

[x] If service endpoint is offline or has connectivity issues (there are a few false positives here, but with the implementation of one or two retries it should be fixed)
[x] If the network is potentially halted (the current example we have with Westend and related paras)
[x] If the network service is having synchronization issues (by checking the difference between best and finalized block)
[x] If the service endpoint has a low performance (by measuring the time it took to query the chain - note that it doesn't remove the latency from the equation yet, needs improvement)
[x] Genesis block and some random block retrieval in the range 0 < block <= chain tip checks for archive nodes.
[x] Verify if node is in healthy state and not syncing

[ ] Votes and conviction checks on both Polkadot and Kusama
[ ] Boot node checks
[ ] Verify certificates expiration date (rpc.ibp.network, sys.ibp.network, rpc.dotters.network, sys.dotters.network)

[dcolley]

@paulormart have these checks been pushed back into the codebase

[paulormart]

They are available at this branch here. Have not been able to merge these changes against the develop branch yet.