-
Notifications
You must be signed in to change notification settings - Fork 25
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
Firehose support for multiple filter and rollups in a single instance #753
Comments
Want to allow something like this:
Where the indented rollups are calculated after each distinct filter set. |
Thoughts on this syntax to link filters and rollups:
This is adding an optional 3rd argument to filter definitions, which is a
This works equally well for flags and using the config file. |
how will this work with AND and OR expressions? Do we need to apply the 3rd rollup_name to all instances?
becomes |
What are you trying to achieve?
Combining multiple sets of filter/rollup combinations to a single instance of firehose caused unexpected data outputs. Due to this it was necessary to tee flow from one instance of firehose to a second instance allowing each instance to utilize it's own filter set and output rollups as required.
The use of two instances effectively doubles the expected CPU/Memory required to implement the solution
If each firehose instance is limited to only a single --filter then any additional rollups that might require a slightly different filter set would require yet another instance to be tee'd and instantiated increasing the footprint further
The request here is to implement a single firehose instance that can take multiple sets of filter criteria and matching rollup criteria optimizing for resources to limit the required compute footprint required.
What is your current work around? (optional)
tee and spawn a new instance of firehose for each --filter --rollup pair required for reporting purposes
cc @kentik-rbarnes please provide examples of sets filter + rollup that can be used for testing.
The text was updated successfully, but these errors were encountered: