Closed wxiaomou closed 1 month ago
/cc @WangLe1321
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: BornChanger, WangLe1321
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Timeline:
2024-05-14 09:36:40.409242215 +0000 UTC m=+1559554.166377786
: :ballot_box_with_check: agreed by WangLe1321.2024-05-14 09:38:11.27476372 +0000 UTC m=+1559645.031899294
: :heavy_multiplication_x::repeat: reset by WangLe1321.2024-05-14 09:38:31.623588617 +0000 UTC m=+1559665.380724186
: :ballot_box_with_check: agreed by WangLe1321.2024-05-15 06:28:24.563299598 +0000 UTC m=+1634658.320435171
: :heavy_multiplication_x::repeat: reset by ti-chi-bot[bot].2024-05-15 12:23:32.74431683 +0000 UTC m=+1655966.501452403
: :ballot_box_with_check: agreed by BornChanger./cherry-pick release-1.5
@BornChanger: new pull request created to branch release-1.5
: #5648.
What problem does this PR solve?
Currently when the federated manager restart we lost the metrics, and the new status metric will start with value 1. In our dashboard we are measuring success/fail backups by increase() function, current implementation will cause we lost the back up status when federated manager restarts.
This PR set the status counter to 0 before it emit the first metric.
What is changed and how does it work?
Code changes
Tests
Side effects
Related changes
Release Notes
Please refer to Release Notes Language Style Guide before writing the release note.