Bug 2210268 - [Fusion-aaS] PagerDuty alerts are not raised
Summary: [Fusion-aaS] PagerDuty alerts are not raised
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-managed-service
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Ohad
QA Contact: Filip Balák
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-26 11:23 UTC by Filip Balák
Modified: 2023-08-09 17:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

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#
Note You need to log in before you can comment on or make changes to this bug.