-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Gather rest client latency and error rate to be able to detect performance regressions #25375
Conversation
Signed-off-by: Damien Grisonnet <dgrisonn@redhat.com>
@dgrisonnet: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/approve |
LGTM giving an opportunity for @aojea to review |
@dgrisonnet I ended changing the regex to avoid getting the host+path and get the host only
|
It doesn't affect this PR since I am not relabeling the URL label to extract the host. Here, I am only exposing a higher-level type information which takes three values: load_balancer, service, and pod to avoid consuming too much resource |
you are the expert here |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, deads2k, dgrisonnet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@dgrisonnet: Updated the
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Collect the latencies and error rates of the proxies in front of the apiserver to be able to detect regression from a particular network proxy. I can be either the load balancers, the services, or direct access via the pod.
The actual queries are based on openshift/cluster-kube-apiserver-operator#1272 and look like the following if they were not one-lined:
rest client 99th percentile of request latency:
rest client average request latency:
rest client error rate:
Note that all the graphs resulting from these queries will have 3 entries, one for each type of proxy.