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 1877735: Adding CodeReady Workspaces metrics to the allowlist / config.yaml #925

Merged
merged 3 commits into from Sep 22, 2020

Conversation

ibuziuk
Copy link
Contributor

@ibuziuk ibuziuk commented Sep 9, 2020

Related CRW issue - https://issues.redhat.com/browse/CRW-927
CodeReady Workspaces team request for sending data via telemetry [Approved for cardinality] - https://docs.google.com/document/d/1WzJrXXCFSFVFLHIKeg0b-lo3wA4S1qPK4Qa7fKdjMKo/edit#heading=h.3im6egcwyu2

Changelog entry format:

  • #925 Adding CodeReady Workspaces metrics to the allowlist

@@ -225,6 +225,17 @@ data:
# (workloads-team, @openshift/openshift-group-b) cluster_master_schedulable reports whether mastersSchedulable=true in
# the scheduler operator. This value is a boolean 0|1
- '{__name__="cluster_master_schedulable"}'
# (codeready workspaces) The number of workspaces with a given status STARTING|STOPPED|RUNNING|STOPPING. Type 'gauge'.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please add a team (github alias) owning these metrics.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the repo is under https://github.com/redhat-developer/codeready-workspaces I do not think we have some team alias

Copy link
Contributor

Choose a reason for hiding this comment

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

We need some contact team internally who are responsible for those metrics.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sure, but can it be an internal slack channel reference?

Copy link
Contributor

Choose a reason for hiding this comment

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

No, its for pinging on github. Ideally a team within openshift org or individual person we can ping when we change/rename/remove metrics.

Copy link
Contributor

Choose a reason for hiding this comment

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

@vparfonov @ibuziuk please add a team alias in the openshift organization where we can ping people in case we run into troubles with those metrics.

@s-urbaniak
Copy link
Contributor

cc @smarterclayton for approval

@s-urbaniak
Copy link
Contributor

side note: You need a bugzilla as we are in feature freeze cycle in OpenShift too.

@s-urbaniak
Copy link
Contributor

ah, i see cardinality has been approved in the linked doc, ok 👍

@s-urbaniak
Copy link
Contributor

/test e2e-aws-operator

@ibuziuk
Copy link
Contributor Author

ibuziuk commented Sep 10, 2020

side note: You need a bugzilla as we are in feature freeze cycle in OpenShift too.

if we can make it for 4.6 that would be ideal otherwise we plan to have it for 4.7
BZ - https://bugzilla.redhat.com/show_bug.cgi?id=1877735

@s-urbaniak s-urbaniak changed the title CRW-927 Adding CodeReady Workspaces metrics to the allowlist / config.yaml Bug 1877735: Adding CodeReady Workspaces metrics to the allowlist / config.yaml Sep 10, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Sep 10, 2020
@openshift-ci-robot
Copy link
Contributor

@ibuziuk: This pull request references Bugzilla bug 1877735, which is invalid:

  • expected the bug to target the "4.6.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 1877735: Adding CodeReady Workspaces metrics to the allowlist / config.yaml

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.

@ibuziuk
Copy link
Contributor Author

ibuziuk commented Sep 11, 2020

folks, I will be on PTO till September 29th, but @vparfonov will follow up on this PR. Please let us know if anything is required on our end to have these metrics in 4.6

@simonpasquier
Copy link
Contributor

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Sep 14, 2020
@openshift-ci-robot
Copy link
Contributor

@simonpasquier: This pull request references Bugzilla bug 1877735, 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
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

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 removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Sep 14, 2020
@s-urbaniak
Copy link
Contributor

one last nit regarding team alias, but I have one last question:

@ibuziuk @vparfonov just to make sure: do we have e2e coverage in CI for those metrics too where we can inspect runtime behavior of prometheus, aka a downloadable metrics dump?

@vparfonov
Copy link
Contributor

one last nit regarding team alias, but I have one last question:

@ibuziuk @vparfonov just to make sure: do we have e2e coverage in CI for those metrics too where we can inspect runtime behavior of prometheus, aka a downloadable metrics dump?

@s-urbaniak AFAIK we don't have any test which covered such cases

@s-urbaniak
Copy link
Contributor

@vparfonov just verified with @lilic, you are covered by OLM tests.

This LGTM minus some contact person/mailing-list alias/github team we can contact in case of issues with the metrics.

@vparfonov
Copy link
Contributor

@s-urbaniak Can we merge this PR as is, after add contact person/mailing-list in separate PR?

@lilic
Copy link
Contributor

lilic commented Sep 21, 2020

@vparfonov no because you need another bugzilla for that, so would be best to do that now. 4.6 code freeze is a week or so away so you still have some time. :) You can also add yourself temporarily and fix in 4.7 to something else?

@vparfonov
Copy link
Contributor

/retest

ibuziuk and others added 3 commits September 21, 2020 19:38
…onfig.yaml

Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
…rics

Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
Co-authored-by: Vitalii Parfonov <vparfono@redhat.com>
@s-urbaniak
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 22, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ibuziuk, s-urbaniak

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 22, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 1fcb682 into openshift:master Sep 22, 2020
@openshift-ci-robot
Copy link
Contributor

@ibuziuk: All pull requests linked via external trackers have merged:

Bugzilla bug 1877735 has been moved to the MODIFIED state.

In response to this:

Bug 1877735: Adding CodeReady Workspaces metrics to the allowlist / config.yaml

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.

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/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants