Skip to content

Comments

Add a relabeled alerts metric#1920

Open
sradco wants to merge 1 commit intoopenshift:masterfrom
sradco:add_alerts_effective_active_at_metric
Open

Add a relabeled alerts metric#1920
sradco wants to merge 1 commit intoopenshift:masterfrom
sradco:add_alerts_effective_active_at_metric

Conversation

@sradco
Copy link

@sradco sradco commented Jan 11, 2026

Add a metric alerts_effective_active_at_timestamp_seconds, that reports the activate time of the alerts after relabeling, for both user and platform alerts.

This enhancements is related to #1822

@openshift-ci openshift-ci bot requested review from moadz and simonpasquier January 11, 2026 09:58
@sradco
Copy link
Author

sradco commented Jan 11, 2026

/assign @simonpasquier

Add a metric alerts_effective_active_at_timestamp_seconds,
that reports the activate time of the alerts after relabeling,
for both user and platform alerts.

Signed-off-by: Shirly Radco <sradco@redhat.com>
@sradco sradco force-pushed the add_alerts_effective_active_at_metric branch from a2ef41c to 45b8ceb Compare January 11, 2026 15:32
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 11, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from simonpasquier. 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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 11, 2026

@sradco: The following test 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/markdownlint 45b8ceb link true /test markdownlint

Full PR test history. Your PR dashboard.

Details

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

Inactive enhancement proposals go stale after 28d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

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

If this proposal 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 Feb 9, 2026
@openshift-bot
Copy link

Stale enhancement proposals rot after 7d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

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

If this proposal 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 Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants