-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add metrics for chain fork work and lengths #5297
Comments
When would they like these by? The earliest I would schedule these would be next sprint (21) and only if the release candidate work is complete |
This is for ZIP 315, to verify whether the recommended "trusted" and "untrusted" confirmation depths make sense and to provide supporting rationale. So not immediately urgent. |
This is blocked by PR #5257 merging, because it changes some of the same code as this ticket. |
Hey team! Please add your planning poker estimate with Zenhub @arya2 @conradoplg @oxarbitrage @teor2345 @upbqdn |
tentatively scheduling this for after the GBT work |
Some of these changes are already made in PR #6235, when I get time, I'll split them out into a separate PR. |
We probably want to delay this until after we've renamed some parts of the state in response to an audit finding. |
This might also depend on #7109, because at the moment we're storing the partial work of the fork, not the cumulative work of the entire chain. |
Motivation
The ZIP editors asked for the following Zebra metrics:
tip height - fork height
)In #6235, we added APIs for these metrics, but we need to track them using prometheus in this ticket:
We already implement these metrics
zcashd
is currently unable to track these metrics, because it doesn't seek out multiple chains in parallel.The text was updated successfully, but these errors were encountered: