[release-3.11] Bug 1890545: Backport Fix decreasing metric counters when reloading HAProxy #25623
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.
This PR is the 3.11 backport of openshift/router#179
The HAProxy router reload process calls
CollectNow()inpkg/router/metrics/haproxy/haproxy.go. Currently,CollectNow()does not updatee.lastScrape, which means it is possible for the normal scrape functionCollect(...)to be called just afterCollectNow(), but before HAProxy has actually reloaded, sinceCollectNow()essentially "resets" the metrics scrape interval.The idea in this PR is to have
CollectNow()set thee.lastScrapetime, sinceCollectNow()is callingscrape()anyways. This will prevent counter metrics from decreasing across reloads since metrics are only saved for reload preservation duringCollectNow()to minimize memory usage.