Bug 1965406 - AlertmanagerReceiversNotConfigured alert fires after a period of time when valid receivers have been setup
Summary: AlertmanagerReceiversNotConfigured alert fires after a period of time when va...
Keywords:
Status: CLOSED DUPLICATE of bug 1904161
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Simon Pasquier
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-27 16:23 UTC by Luke Stanton
Modified: 2024-10-01 18:22 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-04 13:18:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Luke Stanton 2021-05-27 16:23:46 UTC
Description of problem:

AlertmanagerReceiversNotConfigured alerts are firing after a period of time, even though they were setup correctly and worked previously. It appears that the alert is being used more do indicate that a receiver has not been used. In this case a more appropriate name would be AlertmanagerReceiversNotUsed


How reproducible: Consistently


Steps to Reproduce:
1.Setup one or more valid Alertmanager receivers


Actual results:

After a period of time the alert starts firing


Expected results:

The AlertmanagerReceiversNotConfigured would not fire if valid receivers have been configured. An alert named AlertmanagerReceiversNotUsed would be more appropriate when indicating a receiver has not been actively used.


Note You need to log in before you can comment on or make changes to this bug.