-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bug 2007677: Adjust dropped cAdvisor metrics #1402
Conversation
@philipgough: This pull request references Bugzilla bug 2007677, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
We drop some pod-centric metrics from cAdvisor to reduce cardinality. This metrics are available at the slice level.
6be7a0c
to
3402cf5
Compare
@philipgough Can you add the description in PR |
@philipgough: This pull request references Bugzilla bug 2007677, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
/skip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgrisonnet, PhilipGough 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 |
@philipgough: 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. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest |
@philipgough: All pull requests linked via external trackers have merged: Bugzilla bug 2007677 has been moved to the MODIFIED state. 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. |
container_fs_.* metrics doesn't have "container" label after openshift/pull/1402 which caused regression for dashboards using "container" label since it gives empty datapoints for all queries using "container" label in queries containing container_fs_.* metrices. Inorder to fix the dashboards added containerfsSelector in kubernetes-monitoring/kubernetes-mixin/pull/737 and overrided the containerfsSelector default value from container!="" to harmless id!="" in this commit. We really don't need that selector since we dropped the container label in OCP for container_fs_.* metrices but we need to override the selector for the queries involving container_fs_.* to work.
container_fs_.* metrics doesn't have "container" label after openshift/pull/1402 which caused regression for dashboards using "container" label since it gives empty datapoints for all queries using "container" label in queries containing container_fs_.* metrices. Signed-off-by: Jayapriya Pai <janantha@redhat.com>
container_fs_.* metrics doesn't have "container" label after openshift/pull/1402 which caused regression for dashboards using "container" label since it gives empty datapoints for all queries using "container" label in queries containing container_fs_.* metrices. Inorder to fix the dashboards added containerfsSelector in kubernetes-monitoring/kubernetes-mixin/pull/737 and overrided the containerfsSelector default value from container!="" to harmless id!="" in this commit. We really don't need that selector since we dropped the container label in OCP for container_fs_.* metrices but we need to override the selector for the queries involving container_fs_.* to work.
container_fs_.* metrics doesn't have "container" label after openshift/pull/1402 which caused regression for dashboards using "container" label since it gives empty datapoints for all queries using "container" label in queries containing container_fs_.* metrices. Inorder to fix the dashboards added containerfsSelector in kubernetes-monitoring/kubernetes-mixin/pull/737 and overrided the containerfsSelector default value from container!="" to harmless id!="" in this commit. We really don't need that selector since we dropped the container label in OCP for container_fs_.* metrices but we need to override the selector for the queries involving container_fs_.* to work.
openshift/pull/1402 which caused regression for dashboards using container label since it gives empty datapoints for all queries using container label in queries containing container_fs_.* metrices. Inorder to fix the dashboards added containerfsSelector in kubernetes-monitoring/kubernetes-mixin/pull/737 and overrided the containerfsSelector default value from container!= to harmless id!= in this commit. We really don't need that selector since we dropped the container label in OCP for container_fs_.* metrices but we need to override the selector for the queries involving container_fs_.* to work. Signed-off-by: Jayapriya Pai <janantha@redhat.com>
openshift/pull/1402 which caused regression for dashboards using container label since it gives empty datapoints for all queries using container label in queries containing container_fs_.* metrices. Inorder to fix the dashboards added containerfsSelector in kubernetes-monitoring/kubernetes-mixin/pull/737 and overrided the containerfsSelector default value from container!= to harmless id!= in this commit. We really don't need that selector since we dropped the container label in OCP for container_fs_.* metrices but we need to override the selector for the queries involving container_fs_.* to work. Signed-off-by: Jayapriya Pai <janantha@redhat.com>
This change drops pod-centric metrics that have a non empty
container
label. For context it is best to look at the detailed discussion on prometheus-operator/kube-prometheus#1402 and the issues it links to