fix(usage-service): skip usage control payloads#165
Merged
Conversation
Filter CPA usage Pub/Sub refresh control payloads before normalization so they are not stored as empty usage events. Clear the auth snapshot cache when a refresh control message is received, allowing later usage events to reload account metadata. Adds collector coverage for support_refresh and refresh payloads to prevent regressions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Fix CPA v7.1.39+ usage Pub/Sub control payloads being normalized into empty usage events.
Cause
The collector passed every JSON object to usage normalization. Refresh control messages such as
support_refreshandrefreshhave no usage fields, but normalization fills missing model and endpoint values with-.Solution
support_refreshandrefresh.refreshis received.Testing
cd usage-service && go test ./...