You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tracks adding a simple InputMatcher that takes a configurable threshold and will consistently hash the input string, matching if the resulting hash value is above the configured threshold:
match = (hash(input) % 100) > threshold
This would allow users to configure a match rule that will consistently match X% of requests based on a random input string (e.g. a tracing header).
The text was updated successfully, but these errors were encountered:
I would add this as a CustomMatcher extension for use within the SinglePredicate. I don't recall off the top of my head whether we've wired up the extension factory logic here, so that might be part of it
This introduces a new matcher that allows matching on an input value by
computing a hash value and matching if the value % (configured value) is
greater than a configured threshold. This is useful in being able to
define match criteria that should match for a certain % of input values
in a way that is consistent between independent Envoy instances (e.g. it
does not rely on a random input).
Risk Level: Low, new extension
Testing: UTs
Docs Changes: Inline proto docs
Release Notes: n/a
Platform Specific Features: n/a
Fixes#14782
Signed-off-by: Snow Pettersen <snowp@lyft.com>
Tracks adding a simple InputMatcher that takes a configurable threshold and will consistently hash the input string, matching if the resulting hash value is above the configured threshold:
This would allow users to configure a match rule that will consistently match X% of requests based on a random input string (e.g. a tracing header).
The text was updated successfully, but these errors were encountered: