-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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 etcd_server_range_duration_seconds metrics #16866
Comments
I would like to work on this |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
Discussed during sig-etcd triage meeting. This would be a good candidate for a new contributor. The original pr #16902 was abandoned by the previous contributor so we need to recreate this, and add a test. |
Hello @jmhbnz. |
Thanks for volunteering @thedtripp! Assigned to you. Please start by recreating the earlier proposed changes from #16902. Then we need a second commit to add a basic test verifying the new metric works. Let us know how you go and if you have any questions 🙏🏻 /assign @thedtripp |
Most welcome! For a much quicker next contribution we need to update our website community page etcd-io/website#850. If you're interested please feel free to leave a comment and I will assign it to you. Alternatively please take a look at our |
Sure! I'm happy to work on this. |
Hey Team, |
I'm closing this, as it was completed by #17983. Thanks, @thedtripp. Please re-open it @ahrtr / @jmhbnz if you think we need to backport this. |
What would you like to be added?
We already have etcd_server_apply_duration_seconds metrics.
But Range doesn't go through Applier. The only metrics we have about Range timing is
grpc_server_handled_total{grpc_method="Range"}
provided by grpc_middleware. Problem is that this grpc metric also includes timing oflinearizableReadNotify
.Please add etcd_server_range_duration_seconds in txn.Range
Why is this needed?
better observability
The text was updated successfully, but these errors were encountered: