Skip to content

DFBUGS-6192:[release-4.22] Add for: 5m to StorageClientHeartbeatMissed alerts#3879

Open
openshift-cherrypick-robot wants to merge 1 commit into
red-hat-storage:release-4.22from
openshift-cherrypick-robot:cherry-pick-3862-to-release-4.22
Open

DFBUGS-6192:[release-4.22] Add for: 5m to StorageClientHeartbeatMissed alerts#3879
openshift-cherrypick-robot wants to merge 1 commit into
red-hat-storage:release-4.22from
openshift-cherrypick-robot:cherry-pick-3862-to-release-4.22

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #3862

/assign weirdwiz

The StorageClientHeartbeatMissed alerts (warning at 120s,
critical at 300s) fire immediately when the heartbeat
metric crosses the threshold, without any persistence
requirement. Transient metrics scraping delays cause
phantom alerts that fire and auto-resolve within minutes.

Add for: 5m to both alert rules so the condition must
persist for 5 minutes before the alert fires, filtering
out false positives caused by intermittent scrape gaps.

Fixes: https://issues.redhat.com/browse/DFBUGS-6192
Fixes: https://issues.redhat.com/browse/DFBUGS-5644
Signed-off-by: Divyansh Kamboj <dkamboj@redhat.com>
@openshift-ci

openshift-ci Bot commented May 21, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: GitHub didn't allow me to assign the following users: weirdwiz.

Note that only red-hat-storage members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

This is an automated cherry-pick of #3862

/assign weirdwiz

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

openshift-ci Bot commented May 21, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found here.

Details 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

@iamniting iamniting changed the title [release-4.22] Add for: 5m to StorageClientHeartbeatMissed alerts DFBUGS-6192:[release-4.22] Add for: 5m to StorageClientHeartbeatMissed alerts May 25, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels May 25, 2026
@openshift-ci-robot

openshift-ci-robot commented May 25, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-6192](https://redhat.atlassian.net/browse/DFBUGS-6192), which is invalid:

  • expected the bug to target the "odf-4.22" version, but no target version was set

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.

Details

In response to this:

This is an automated cherry-pick of #3862

/assign weirdwiz

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.

@iamniting

Copy link
Copy Markdown
Member

@weirdwiz pls sort the bug acks, So that we can merge the Pr.

@iamniting

Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot

openshift-ci-robot commented May 26, 2026

Copy link
Copy Markdown

@iamniting: This pull request references [Jira Issue DFBUGS-6192](https://redhat.atlassian.net/browse/DFBUGS-6192), which is invalid:

  • expected the bug to target the "odf-4.22" version, but no target version was set

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.

Details

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting jira/valid-reference Indicates that this PR references a valid jira ticket of any type

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants