Beacon-chain size graph feature

[gobitfly]

Beacon-chain size graph feature

[SjonHortensius]

I think you should poll prysm or lighthouse to add this to their API. For example, lighthouse has /node/health which seems like a good candidate

The alternative would require this explorer to have access to the datadir of the beacon node (which it doesn't necessarily have) or do some pretty random assumptions about the storage requirements of certain data

[guybrush]

We could expose grafana with node-exporter from nodes with running validators on it.

The thing is that this makes the explorer much less trivial to run.

Not sure about this yet, if you come up with some cool way to solve it we are definitely open for suggestions and/or PRs!

[ncitron]

I asked over at Prysm's discord what they thought about adding a chain size API endpoint, but they said that since the chain db size is client specific, it doesn't belong in the ethereum 2.0 api. I'll have to take a look at how the metrics are exposed via grafana when I get a chance.

[terencechain]

Chain size is largely determined by the type of the node the operator runs. One can choose to run a validator only node (2.5GB) or an archival node (30GB) today. The differences is how often the node saves the state

[ncitron]

Chain size is largely determined by the type of the node the operator runs. One can choose to run a validator only node (2.5GB) or an archival node (30GB) today. The differences is how often the node saves the state

Thats true, which is why I was thinking of doing something like https://etherscan.io/chartsync/chaindefault. It'd be a pain to implement since it would require messing around with all the clients, but would certainly be a very useful graph for people to have access to.

[Buttaa]

added to internal PM tool

[Buttaa]

added to internal PM tool