chore(bridge-withdrawer): accumulating counter instead of guage for settled value #1814
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.
Summary
Replaces the guage metric
batch_total_settled_value
with the counter metricaccumulated_settled_value
Background
The guage metric was not useful because we were not capturing the guage at each packet time, it was most likely going to always be zero. Instead replace with a counter which we can run a rate on to see the total amount of flow out. Because this is strictly increasing we aren't subject to different outputs with different scraping intervals.
Changes
batch_total_settled_value
and replace withaccumulated_settled_value
Testing
How are these changes tested?
Changelogs
Changelogs updated
Metrics
batch_total_settled_value
accumulated_settled_value
metricBreaking Changelist
This is technically speaking a breaking change on the metric interface, however the existing metric never worked, so I wouldn't consider truly breaking.