-
Notifications
You must be signed in to change notification settings - Fork 3
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
Enhanced age filter to perform limit calcs internally using dynamically fetched limit setting #4
Conversation
Baseline enhancements to dynamically query a limit service and perform limit calculations internally
I know the ascidoc needs attention; I'm not sure how to update it from the comments in the source file. |
❌ Author of the following commits did not sign a Contributor Agreement: Please, read and sign the above mentioned agreement if you want to contribute to this project |
I filed a contributor agreement on another pull request. |
Let's see if I can deploy thisenhanced age filter
I had to receate the repo: It is here: https://github.com/richard-mauri/logstash-filter-age |
closing and opening a new pr |
This enhancement to the logstash age filter plugin optionally invokes a remote "limit service" to acquire a limit setting. The limit service can be polled at a scheduled interval.
The age plugin then performs the caculation if the event is older than that limit and sets a field if it is or not.
The
This was motivated by the need to be able to remove hard-coded limit setttings and associated calculation from the pipeline filter config file, and instead query and dynamically the limit settings without changing a config file and restarting or signalling logstash.
It also demonstrates how to use the elasticsearch cluster settings metadata as the limit service.