This bug was initially created as a copy of Bug #2219843 I am copying this bug because: We need some changes in the UI after the changes in Ramen are made. This BZ is to track the UI work. Description of problem (please be detailed as possible and provide log snippests): Version of all relevant components (if applicable): ceph version 17.2.6-70.0.TEST.bz2119217.el9cp (6d74fefa15d1216867d1d112b47bb83c4913d28f) quincy (stable) ODF 4.13.0-219.snaptrim ACM 2.8 Ga'ed, Submariner v0.15.0-rc1 (globalnet enabled) OCP 4.13.0-0.nightly-2023-06-20-224158 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. On a RDR setup, when lastGroupSyncTime is delayed beyond 2 and 3x sync interval, a warning and an alert is shown on the DR monitoring dashboard but the challenge is that ACM observability has to be explicitely enabled to access this dashboard and the dashboard doesn't take subscription based workloads into account to showcase such alerts or any data to say. The idea is to induce those alerts directly into ramen and show on OCP alert menu which would avoid the need to either enable ACM observability and the risk to miss updates on suscription based workloads. 2. 3. Actual results: Expected results: Induce DR dashboard alerts directly into ramen when lastGroupSyncTime is delayed Additional info: