-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for query/reply messages to Downsampling #1797
Add support for query/reply messages to Downsampling #1797
Conversation
In the current implementation, rules within the same Downsampling config share the same state if configured on the same keyexpr. Having message types within the rules can lead users to configure different messages types within different rules with same keyexpr, which would produce the same result as having all message types within the same rule, i.e downsampling on the whole set of messages instead of doing so seperately for each type.
PR missing one of the required labels: {'dependencies', 'bug', 'new feature', 'internal', 'enhancement', 'breaking-change', 'documentation'} |
Clarification regarding my commit message for 963eb84: two rules on the same keyexpr would have the last rule in the list overwrite the previous one, which further supports why message types need to be moved out of the rules list. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1797 +/- ##
==========================================
+ Coverage 70.35% 70.90% +0.54%
==========================================
Files 359 360 +1
Lines 64617 65135 +518
==========================================
+ Hits 45460 46182 +722
+ Misses 19157 18953 -204 ☔ View full report in Codecov by Sentry. |
Adds query/reply message filters to Downsampling interceptor. Query/reply message types are respectively named
"query"
and"reply"
, with the addition of"push"
which is the previously supported Publication message type.Downsampling config with different message types will apply its rules on all these message types as one flow of messages. Seperate Downsampling configurations with one type each will apply the rules per message type.
Also changes Downsampling config to accept a list of flows instead of a single one, to limit the need to duplicate a downsampling conf for query/reply messages which go in opposite flows.
Note that this PR breaks compatibility with previous format of Downsampling configuration.