Provide a way to detect next proposal time about nimbus-eth2 HOT 9 CLOSED

There's more value in keeping REST calls to be as close to only-beacon-API as possible. The more Nimbus-specific calls there are, the less interoperability, which partly defeats the point.

Metrics weren't ever broadly interoperable to begin with, so better to put client-specific things in metrics where feasible.

from nimbus-eth2.

nextProposalSlot is in the same Slot end log as nextActionWait.

from nimbus-eth2.

Okay, but can we get a metric?

from nimbus-eth2.

Would this one work for you?

• #6028

Proposals are not so frequent, so it would be set to Inf if time to next one is unknown.

And, also added a boolean one for sync committee – they last ~27hrs though with a signature every 12 seconds, but during that time profit is massively increased so it may still be worthwhile to delay maintenance to the next day if it's not critical?
If you don't need sync committee I can also remove it again from the PR.

from nimbus-eth2.

Sync committee metric is also cool, thanks for this.

from nimbus-eth2.

You really need a metric for this? We could provide a REST call.

from nimbus-eth2.

Also, metrics have more uses than REST API calls. You can actually graph how often and how busy your node is.

from nimbus-eth2.

#6028

from nimbus-eth2.

I checked Prometheus for values of the new metric and it appears to work:

Thanks.

from nimbus-eth2.