Bug 2232242: Refactoring metrics creation and initialisation #138
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Metrics were previously created regardless of metro-dr or regional-dr. This has now changed, metrics are not created for metro-dr. The metrics instance creation is also moved from DRPC instance creation to updating DRPC condition, this is done so as not to initialize and set the default value as 0.
The values now refer to DRPC status and not VRG. we update DPRC LastGroup statuses based on the availability of VRG lastGroupSyncTime and the Relocate action. In case we do not get VRG, metrics will have the previous or the last known value from DRPC.
Removed 0 value filtering from alerts. So alerts are fired when metrics have zero value which is set based on DRPC lastGroupSynctime.
BZ: 2232242