[agent] Do not increment data loss counters on the first client batch #2028
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.
Which problem is this PR solving?
In #2010, the counters are always incremented by the delta from current client stats and the previously recorded values. However, when previous values are zero, as could be the case when the client has been running for a while but agent was just restarted, the delta could be very large and not reflective of the incremental change since the previous batch (which the agent did not see), causing massive spikes in metrics and messing up the totals.
Short description of the changes