Skip to content

Conversation

@bkhizgiy
Copy link

Following this JIRA issue https://issues.redhat.com/browse/MON-3940

Related to this PRs for adding metrics on the MTV side:
kubev2v/forklift#916
kubev2v/forklift#932
kubev2v/forklift#978

@openshift-ci openshift-ci bot requested review from jan--f and marioferh September 10, 2024 08:50
@fabiand
Copy link

fabiand commented Sep 10, 2024

@simonpasquier please review

Copy link
Contributor

@simonpasquier simonpasquier left a comment

Choose a reason for hiding this comment

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

You'd need to configure recording rules aggregating on the allowed labels:

  • status
  • provider
  • mode
  • target

If the metrics are emitted by a single container then you can do:

record: cluster:mtv_migrations_status_total:max
expr: max by(status, provider, mode, target) (mtv_migrations_status_total)

otherwise you should probably sum

record: cluster:mtv_migrations_status_total:sum
expr: sum by(status, provider, mode, target) (mtv_migrations_status_total)

@simonpasquier
Copy link
Contributor

simonpasquier commented Sep 10, 2024

/retitle MON-3940: Add the collection of MTV migration metrics to Telemetry
/hold

until explicit approval

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 10, 2024
@openshift-ci openshift-ci bot changed the title Add the collection of MTV migration metrics to Telemetry MON-3940: Add the collection of MTV migration metrics to Telemetry Sep 10, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 10, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 10, 2024

@bkhizgiy: This pull request references MON-3940 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.18.0" version, but no target version was set.

In response to this:

Following this JIRA issue https://issues.redhat.com/browse/MON-3940

Related to this PRs for adding metrics on the MTV side:
kubev2v/forklift#916
kubev2v/forklift#932
kubev2v/forklift#978

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 openshift-eng/jira-lifecycle-plugin repository.

@bkhizgiy
Copy link
Author

@simonpasquier Thanks for the review. Should the recording rule be part of the MTV code, or can we specify the expression in the whitelist? This metric consists only of the mentioned fields, so there aren't any labels to remove or modify.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 14, 2024
@fabiand
Copy link

fabiand commented Sep 19, 2024

@simonpasquier any update?

@simonpasquier
Copy link
Contributor

Should the recording rule be part of the MTV code, or can we specify the expression in the whitelist?

MTV code. The telemetry allow-list only references metric names (and labels).

This metric consists only of the mentioned fields, so there aren't any labels to remove or modify.

We still ask to remove the labels that are useless to keep at the Telemetry server level like instance and pod.

@simonpasquier
Copy link
Contributor

#
# cluster:mtv_migrations_status_total is the total number of VM migrations running on the cluster,
# labeled with {status}, {provider}, {mode}, and {target}.
- '{__name__="mtv_migrations_status_total"}'
Copy link
Contributor

@juzhao juzhao Sep 25, 2024

Choose a reason for hiding this comment

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

the metrics name mtv_migrations_status_total is not the same as cluster:mtv_migrations_status_total in the annotation
cluster:mtv_migrations_status_total is the total number of VM migrations running on the cluster,
maybe should be cluster:mtv_migrations_status_total:sum as @simonpasquier mentioned in #2461 (review)

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 5, 2024
@bkhizgiy
Copy link
Author

bkhizgiy commented Nov 5, 2024

Following the comments, I’ve added a new recording rule for MTV in this PR.
I’ve also updated this PR with the new rule name accordingly.
Please let me know if anything else is needed.

yaacov pushed a commit to kubev2v/forklift that referenced this pull request Nov 25, 2024
Following the request of adding recording rule in
openshift/cluster-monitoring-operator#2461

Signed-off-by: Bella Khizgiyaev <[email protected]>
@fabiand
Copy link

fabiand commented Nov 29, 2024

kubev2v/forklift#1172 got merged - what is needed to move this PR forward?

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 29, 2024
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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-sigs/prow repository.

@sradco
Copy link

sradco commented Dec 9, 2024

Hi @bkhizgiy, looks like the PR needs a rebase. Is there anything else keeping thos PR from getting merged?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2025

@bkhizgiy: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/rules 9dd664b link true /test rules
ci/prow/okd-scos-images 9dd664b link true /test okd-scos-images
ci/prow/shellcheck 9dd664b link true /test shellcheck
ci/prow/unit 9dd664b link true /test unit
ci/prow/generate 9dd664b link true /test generate
ci/prow/e2e-aws-ovn-upgrade 9dd664b link true /test e2e-aws-ovn-upgrade
ci/prow/jsonnet-fmt 9dd664b link true /test jsonnet-fmt
ci/prow/e2e-aws-ovn 9dd664b link true /test e2e-aws-ovn
ci/prow/images 9dd664b link true /test images
ci/prow/golangci-lint 9dd664b link true /test golangci-lint
ci/prow/vendor 9dd664b link true /test vendor
ci/prow/verify 9dd664b link true /test verify
ci/prow/e2e-agnostic-operator 9dd664b link true /test e2e-agnostic-operator
ci/prow/e2e-aws-ovn-techpreview 9dd664b link true /test e2e-aws-ovn-techpreview
ci/prow/e2e-hypershift-conformance 9dd664b link true /test e2e-hypershift-conformance
ci/prow/go-fmt 9dd664b link true /test go-fmt

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 18, 2025
@fabiand
Copy link

fabiand commented May 15, 2025

Folks. I am really not sure what can be done to get this merged.

@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 15, 2025
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Jul 15, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 15, 2025

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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-sigs/prow repository.

@fabiand
Copy link

fabiand commented Oct 13, 2025

/reopen

@openshift-ci openshift-ci bot reopened this Oct 13, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2025

@fabiand: Reopened this PR.

In response to this:

/reopen

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-sigs/prow repository.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 13, 2025

@bkhizgiy: This pull request references MON-3940 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

In response to this:

Following this JIRA issue https://issues.redhat.com/browse/MON-3940

Related to this PRs for adding metrics on the MTV side:
kubev2v/forklift#916
kubev2v/forklift#932
kubev2v/forklift#978

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bkhizgiy
Once this PR has been reviewed and has the lgtm label, please assign simonpasquier for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

solenoci added a commit to solenoci/cluster-monitoring-operator that referenced this pull request Nov 11, 2025
Continuation of https://issues.redhat.com/browse/MON-3940.

Previous outdated PR: openshift#2461

As the previous PR was stale and the person who created the PR is not
longer working on it, I recreated the PR.

Ref: https://issues.redhat.com/browse/MTV-1370

Signed-off-by: Stefan Olenocin <[email protected]>
@solenoci
Copy link
Contributor

solenoci commented Nov 11, 2025

I recreated the PR here: #2743 as Bella is no longer responsible for it. Feel free to close if you don't need it.

solenoci added a commit to solenoci/cluster-monitoring-operator that referenced this pull request Nov 24, 2025
Continuation of https://issues.redhat.com/browse/MON-3940.

Previous outdated PR: openshift#2461

As the previous PR was stale and the person who created the PR is not
longer working on it, I recreated the PR.

Ref: https://issues.redhat.com/browse/MTV-1370

Signed-off-by: Stefan Olenocin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants