Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1965406

Summary:	AlertmanagerReceiversNotConfigured alert fires after a period of time when valid receivers have been setup
Product:	OpenShift Container Platform	Reporter:	Luke Stanton <lstanton>
Component:	Monitoring	Assignee:	Simon Pasquier <spasquie>
Status:	CLOSED DUPLICATE	QA Contact:	Junqi Zhao <juzhao>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	alegrand, anpicker, aos-bugs, broose, erooth, kakkoyun, pkrupa, pnair, stwalter
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-04 13:18:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.