-
Notifications
You must be signed in to change notification settings - Fork 543
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
Recording rule for Network Programming Latency #557
Conversation
Hi @oxddr. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
6d0badc
to
ba7c9ea
Compare
/assign @mm4tt |
/ok-to-test |
clusterloader2/pkg/prometheus/manifests/default/prometheus-serviceMonitorKubeProxy.yaml
Outdated
Show resolved
Hide resolved
You'll also need a kube-proxy service that was temporarily removed in #528 |
ba7c9ea
to
6af3b98
Compare
/retest |
This rule will be used in the Network Programming Latency dashboard. It's recommended by Prometheus documentation to use recording rules for dashboards, see https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/ I also modified the kube-proxy scrape interval, as now thanks to the recording rule we should be able to scrape more often.
45b10d4
to
2a4f136
Compare
2a4f136
to
ad6174f
Compare
ad6174f
to
6143c02
Compare
@mm4tt PTAL |
14b4b63
to
e94a625
Compare
1. Fix incorrect metrics names and use record rule in dashboard. 2. Use environmental variables to gate kube-proxy scrapping. 3. Change framework so it ignores empty manifests
e94a625
to
1ebb44f
Compare
PTAL |
Thanks! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mm4tt, oxddr 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 |
This is based on work by @mm4tt in #430.