Adjust dual read monitoring data match logic and remove log rate limiter #968
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.
Dual read monitoring have been having tons of false-positive uri property mismatches. We used a rate limiter logger which was flooded by uri logs and starved critical logs from service and cluster properties.
Changes
Test Done
Unit tests.
Manual test with QEI d2-proxy.
Log snippet shows the data matches sequence for service "workplaceTypeTaxonomyVersions", its cluster "DataMan" and the uris (I turned debug level log to info level just to show the logs):