Update kvstore_duration_operation_seconds to not include rate-limiting latency #27396
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before,
kvstore_duration_operation_seconds
metric included time spent in rate-limiting.Now it does not include rate-limited time spent.
This change makes the metric more useful when troubleshooting if propagation delays are caused by slow kvstore or rate-limiting.
Users can still observe delays caused by rate-limiting using metric
api_limiter_wait_duration_seconds