[release-4.13] OCPBUGS-14251: Add new web console usage metrics

[jerolimov]

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

Fixes: OCPBUGS-12903

This is a manual backport of #1910 and the final PR to add this metrics to 4.13 (not 4.13.0)

Cherry-pick worked fine without any conflict. I just added another CHANGELOG line for 4.13.

[openshift-ci-robot]

@jerolimov: This pull request references Jira Issue OCPBUGS-14251, which is invalid:

• expected dependent Jira Issue OCPBUGS-12903 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA instead

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

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is a manual backport of #1970

Cherry-pick worked fine without any conflict. I just added another CHANGELOG line for 4.13.

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]

@jerolimov: This pull request references Jira Issue OCPBUGS-14251, which is invalid:

• expected dependent Jira Issue OCPBUGS-12903 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA instead

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

In response to this:

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

Fixes: OCPBUGS-12903

This is a manual backport of #1970 and the final PR to add this metrics to 4.13 (not 4.13.0)

Cherry-pick worked fine without any conflict. I just added another CHANGELOG line for 4.13.

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.

[jerolimov]

/cc @simonpasquier @jan--f @raptorsun @sanketpathak

[jerolimov]

/assign @simonpasquier

[simonpasquier]

not strictly needed as it's only for internal use.

[simonpasquier]

/lgtm
/label backport-risk-assessed

[jerolimov]

/retest

[jerolimov]

/jira refresh

[openshift-ci-robot]

@jerolimov: This pull request references Jira Issue OCPBUGS-14251, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.13.z) matches configured target version for branch (4.13.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-12903 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
• dependent Jira Issue OCPBUGS-12903 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
• bug has dependents

Requesting review from QA contact:
/cc @sanketpathak

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

/jira 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.

[sanketpathak]

/label cherry-pick-approved

[openshift-ci]

@sanketpathak: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

/label cherry-pick-approved

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.

[simonpasquier]

/assign @juzhao

[juzhao]

FYI: I see the 4.14 PR is merged, checked with 4.14.0-0.nightly-2023-06-05-112833, the 7 added metrics are not in telemeter server allow list, https://github.com/rhobs/configuration/blob/main/configuration/telemeter/metrics.json
so we can not find the metrics from telemeter server, should also submit PR to add metrics to telemeter server allow list

[openshift-ci-robot]

@jerolimov: This pull request references Jira Issue OCPBUGS-14251, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.13.z) matches configured target version for branch (4.13.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-12903 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
• dependent Jira Issue OCPBUGS-12903 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
• bug has dependents

Requesting review from QA contact:
/cc @sanketpathak

In response to this:

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

Fixes: OCPBUGS-12903

This is a manual backport of #1910 and the final PR to add this metrics to 4.13 (not 4.13.0)

Cherry-pick worked fine without any conflict. I just added another CHANGELOG line for 4.13.

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.

[jerolimov]

Thanks @juzhao for the review.

I opened #1997 to fix these issues also on the master and cherry-picked the commit into this PR as well.

Can you please take a fresh look. Thanks :)

[jerolimov]

FYI: I see the 4.14 PR is merged, checked with 4.14.0-0.nightly-2023-06-05-112833, the 7 added metrics are not in telemeter server allow list, https://github.com/rhobs/configuration/blob/main/configuration/telemeter/metrics.json so we can not find the metrics from telemeter server, should also submit PR to add metrics to telemeter server allow list

Thanks @juzhao for that information. I wasn't aware of that before and created rhobs/configuration#510 for that. Did you know who can take a look?

cc @simonpasquier

[juzhao]

/lgtm
for rhobs/configuration#510, maybe @philipgough can help on review the PR

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerolimov, juzhao, simonpasquier

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:

• OWNERS [simonpasquier]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[juzhao]

/label cherry-pick-approved

[jerolimov]

/retest

[openshift-ci-robot]

@jerolimov: Jira Issue OCPBUGS-14251: All pull requests linked via external trackers have merged:

• openshift/cluster-monitoring-operator#1976

Jira Issue OCPBUGS-14251 has been moved to the MODIFIED state.

In response to this:

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

Fixes: OCPBUGS-12903

This is a manual backport of #1910 and the final PR to add this metrics to 4.13 (not 4.13.0)

Cherry-pick worked fine without any conflict. I just added another CHANGELOG line for 4.13.

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-merge-robot]

Fix included in accepted release 4.13.0-0.nightly-2023-06-12-183948