8000 chore(controller)!: tune grpc handling time histogram buckets by olix0r · Pull Request #14130 · linkerd/linkerd2 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore(controller)!: tune grpc handling time histogram buckets #14130

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

Merged
merged 1 commit into from
Jun 14, 2025

Conversation

olix0r
Copy link
Member
@olix0r olix0r commented Jun 13, 2025

The default histogram buckets for gRPC handling time are tuned for short-lived requests. Our controllers tend to serve long-lived response streams, which are counted at the maximum bucket.

This change adjusts the histogram buckets to better reflect the characteristics of our response streams, which have a default 5m idle timeout and 1h max lifetime.

The default histogram buckets for gRPC handling time are tuned for short-lived
requests. Our controllers tend to serve long-lived response streams, which are
counted at the maximum bucket.

This change adjusts the histogram buckets to better reflect the characteristics
of our response streams, which have a default 5m idle timeout and 1h max
lifetime.
@olix0r olix0r requested a review from a team as a code owner June 13, 2025 21:17
@olix0r olix0r enabled auto-merge (squash) June 13, 2025 21:17
@olix0r olix0r changed the title chore(controller): tune grpc handling time histogram buckets chore(controller)!: tune grpc handling time histogram buckets Jun 13, 2025
@olix0r olix0r merged commit 7e5943a into main Jun 14, 2025
97 of 102 checks passed
@olix0r olix0r deleted the ver/grpc-go-histgo branch June 14, 2025 01:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0