Add previous values to app usage events #569
Closed
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.
CC presents the app usage events in chronological order, but this doesn't guarantee that they'll progress in that order through micro-service pipeline (such as Abacus). There may be random communication delays, errors, retries, etc along the processing of each event, which may disturb the initial chronological order.
This PR tries to solve these out-of-order submissions by using special formulas based on previous state as described in cloudfoundry-attic/cf-abacus#231