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

[release-1.2] monitoring: Fix wrong calculation for KubeVirtVMIExcessiveMigrations in an edge case #12358

Conversation

kubevirt-bot
Copy link
Contributor

This is an automated cherry-pick of #12209

/assign orenc1

Fix wrong KubeVirtVMIExcessiveMigrations alert calculation in an upgrade scenario.

…in an edge case

There is an edge case, usually during an upgrade, in which two or more different virt-controllers are reporting the 'kubevirt_vmi_migration_succeeded' metric
for the same migration (VMIM) on the same VMI. In that case, we need to count that migration only once regardless of it being reported multiple times
for the purpose of firing the alert about excessive amount of migrations in the last 24 hours.
The new PromQL isolates the entries with different VMIMs, then sets the value of '1' to all of them, and then we're summing by the pair of vmi and its namespace.

Signed-off-by: Oren Cohen <ocohen@redhat.com>
@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Jul 16, 2024
@kubevirt-bot kubevirt-bot added sig/buildsystem Denotes an issue or PR that relates to changes in the build system. sig/observability Denotes an issue or PR that relates to observability. size/M labels Jul 16, 2024
@enp0s3
Copy link
Contributor

enp0s3 commented Jul 16, 2024

/approve

@kubevirt-bot
Copy link
Contributor Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enp0s3

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 16, 2024
@orenc1
Copy link
Contributor

orenc1 commented Jul 16, 2024

/retest

@orenc1
Copy link
Contributor

orenc1 commented Jul 16, 2024

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Jul 16, 2024
@kubevirt-commenter-bot
Copy link

/retest-required
This bot automatically retries required jobs that failed/flaked on approved PRs.
Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

@kubevirt-bot kubevirt-bot merged commit 1f0f4e1 into kubevirt:release-1.2 Jul 17, 2024
34 checks passed
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/buildsystem Denotes an issue or PR that relates to changes in the build system. sig/observability Denotes an issue or PR that relates to observability. size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants