Initial barebone flask app to display "network health".
Admittedly, this is a very rough draft, and this repo might not end up being the best location for this app to live. But, coupling it with eth-portal seemed like a solid starting point, as I discussed with @mrferris.
The eventual goal of this dashboard is a quick-look at the network to evaluate network health. It currently supports a couple of routes.
/ (home) - pings every bootnode to see if they're online
/header/[0x-prefixed-block-hash] - performs a recursive find content from the network to test data availability
/block_body/[0x-prefixed-block-hash] - performs a recursive find content from the network to test data availability
/receipts/[0x-prefixed-block-hash] - performs a recursive find content from the network to test data availability
Open to any and all ideas on how to improve the content displayed here, projects structure, anything else. Again, this code is VERY ROUGH, and I expect to go through multiple refactors before merging. But wanted to open this as a draft and collect suggestions / avoid any duplicate work w/ @mrferris.
I also have this up and deployed on the cloud, attached to a trin node. So, theoretically anybody can visit it. But I need to do a little more hardening before sharing that endpoint for others to test out.
What was wrong?
Initial barebone flask app to display "network health". Admittedly, this is a very rough draft, and this repo might not end up being the best location for this app to live. But, coupling it with
eth-portal
seemed like a solid starting point, as I discussed with @mrferris.The eventual goal of this dashboard is a quick-look at the network to evaluate network health. It currently supports a couple of routes.
/
(home) - pings every bootnode to see if they're online/header/[0x-prefixed-block-hash]
- performs a recursive find content from the network to test data availability/block_body/[0x-prefixed-block-hash]
- performs a recursive find content from the network to test data availability/receipts/[0x-prefixed-block-hash]
- performs a recursive find content from the network to test data availabilityOpen to any and all ideas on how to improve the content displayed here, projects structure, anything else. Again, this code is VERY ROUGH, and I expect to go through multiple refactors before merging. But wanted to open this as a draft and collect suggestions / avoid any duplicate work w/ @mrferris.
I also have this up and deployed on the cloud, attached to a trin node. So, theoretically anybody can visit it. But I need to do a little more hardening before sharing that endpoint for others to test out.
How was it fixed?
Summary of approach.
To-Do
[ ] Clean up commit history
[ ] Add entry to the release notes
Cute Animal Picture
![put a cute animal picture link inside the parentheses]()