Bug 2210268

Summary:	[Fusion-aaS] PagerDuty alerts are not raised
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Filip Balák <fbalak>
Component:	odf-managed-service	Assignee:	Ohad <omitrani>
Status:	NEW ---	QA Contact:	Filip Balák <fbalak>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.12	CC:	ebenahar, odf-bz-bot
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:		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 Filip Balák 2023-05-26 11:23:36 UTC

Description of problem:
If a Fusion aaS cluster is configured according to a PagerDuty guide [1] and the cluster is in unhealthy state then there are no alerts in PagerDuty raised.

Version-Release number of selected component (if applicable):
managed-fusion-agent-index:4.12.3-16.05
OCP 4.12

How reproducible:
3/3

Steps to Reproduce:
1. Configure Fusion-aaS cluster with PagerDuty alerting according to the guide [1].
2. Scale down to 0 a ceph cluster resource (osd/mgr/mon/mds).
3. Wait at least 15 minutes for the system to send an alert.
4. Check PagerDuty system.

Actual results:
There are no Alerts in PagerDuty.

Expected results:
Proper alerts should be raised.

Additional info:
[1] https://docs.google.com/document/d/1hUydHjMXgp9_3XDOS5VOHVPKP_Kj0a0eSyoOjcs7-cQ/edit#