Description of problem (please be detailed as possible and provide log snippests): The replication history graph on the DR dashboard is providing very unclear information. The ramen metric "ramen_last_sync_timestamp_seconds" is not suited for the graph and it results to confuse the users. This graph is unnecessary and leads to confusion, so the decision is to remove this graph from 4.13. Version of all relevant components (if applicable): 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? 100% Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Enable ACM observability and whitelist DR metrics: https://docs.google.com/document/d/1hl9BOShVpHQKZPXmMZJes3rrQdvy3IHBHmQSfqMSJr8/edit?usp=sharing 2. On the DR hub cluster, Go to All Cluster -> Data services -> Data policies -> Overview -> change the application dropdown from All applications to a particular application. Actual results: The intention of the graph is to convey the replication delay like whether it is matching the drPolicy scheduled interval. But for users this graph is really difficult to makesense out of it. Expected results: Remove this graph for 4.13. Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:3742