Skip to content
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

bug 1757547: charts/openshift-metering: Update cpu/memory usage promqueries to handle many to many matching error #958

Conversation

chancez
Copy link
Contributor

@chancez chancez commented Sep 27, 2019

These queries were returning many to many matching errors on the
group_left that I didn't end up diagnosing, but I discovered we can
remove it since the container level metrics got the node name field that
we were joining from kube_pod_info. This simplifies them overall.
Additionally, I bumped up the window size for when we take the rate of
the CPU.

@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 27, 2019
@chancez chancez force-pushed the fix_metrics_import_many_to_many branch from f7195ff to 33cf322 Compare September 27, 2019 20:17
@chancez
Copy link
Contributor Author

chancez commented Sep 27, 2019

/hold
I want to file a bug on this and possibly backport to 4.2

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 27, 2019
@chancez
Copy link
Contributor Author

chancez commented Sep 27, 2019

This PR and others are blocked until #960 merges

These queries were returning many to many matching errors on the
group_left that I didn't end up diagnosing, but I discovered we can
remove it since the container level metrics got the node name field that
we were joining from kube_pod_info. This simplifies them overall.
Additionally, I bumped up the window size for when we take the rate of
the CPU.

Also updates CPU usage query to use a 5 minute window instead of 1
minute for better accuracy and alignment with upstreams values.
@chancez chancez force-pushed the fix_metrics_import_many_to_many branch from 33cf322 to 2a070e0 Compare September 30, 2019 19:56
Copy link
Member

@timflannagan timflannagan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 1, 2019
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chancez, timflannagan1

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@chancez chancez changed the title charts/openshift-metering: Update cpu/memory usage promqueries bug 1757547: charts/openshift-metering: Update cpu/memory usage promqueries to handle many to many matching error Oct 1, 2019
@openshift-ci-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Oct 1, 2019
@openshift-ci-robot
Copy link

@chancez: This pull request references Bugzilla bug 1757547, which is invalid:

  • expected the bug to target the "4.3.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

bug 1757547: charts/openshift-metering: Update cpu/memory usage promqueries to handle many to many matching error

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.

@chancez
Copy link
Contributor Author

chancez commented Oct 1, 2019

/bugzilla refresh

@openshift-ci-robot
Copy link

@chancez: This pull request references Bugzilla bug 1757547, 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.

In response to this:

/bugzilla refresh

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.

@openshift-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Oct 1, 2019
@chancez
Copy link
Contributor Author

chancez commented Oct 1, 2019

/cherry-pick release-4.2

@openshift-cherrypick-robot

@chancez: once the present PR merges, I will cherry-pick it on top of release-4.2 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.2

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.

@chancez
Copy link
Contributor Author

chancez commented Oct 1, 2019

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 1, 2019
@openshift-merge-robot openshift-merge-robot merged commit 16827b0 into kube-reporting:master Oct 1, 2019
@openshift-ci-robot
Copy link

@chancez: All pull requests linked via external trackers have merged. Bugzilla bug 1757547 has been moved to the MODIFIED state.

In response to this:

bug 1757547: charts/openshift-metering: Update cpu/memory usage promqueries to handle many to many matching error

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.

@openshift-cherrypick-robot

@chancez: #958 failed to apply on top of branch "release-4.2":

error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	charts/openshift-metering/values.yaml
Falling back to patching base and 3-way merge...
Auto-merging charts/openshift-metering/values.yaml
CONFLICT (content): Merge conflict in charts/openshift-metering/values.yaml
Patch failed at 0001 charts/openshift-metering: Update cpu/memory usage promqueries

In response to this:

/cherry-pick release-4.2

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.

@chancez chancez deleted the fix_metrics_import_many_to_many branch October 1, 2019 23:32
@chancez
Copy link
Contributor Author

chancez commented Oct 1, 2019

The cherry-pick needs #962 since that has changes this PR requires (which came from #960)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants