Description of problem (please be detailed as possible and provide log
snippests):
The replication history graph under the DR monitoring dashboard is showing incorrect values. After 60 Minutes the graph value is reset to 0 and starts increasing from 0.

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?
No

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?
1--%

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Create an RDR DRPolicy with a sync interval of 5 minutes.
2. Apply the DRPolicy to any ACM application set type applications.
3. Wait for the last sync time to be reported for the application under "data policy"   column on the ACM application page.
4. Once replication is started, disable the DR for this application from UI(just to manually break the replication, once DRPC is marked as deleted it won't change the last sync time).
4. Enable the ACM observability and whitelist the metrics. (for more: https://docs.google.com/document/d/1hl9BOShVpHQKZPXmMZJes3rrQdvy3IHBHmQSfqMSJr8/edit?usp=sharing).
5. Go to the replication history graph under DR dashboard, Data services -> Data policies -> Overview -> select the application set name from the dropdown.
6. Exactly after 60 mins, the graph started showing wrong data in the graph.

Actual results:
The replication history graph is showing wrong data

Expected results:
it should always display the correct replication sync status.

Additional info: