Skip to content
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

Module/Prospector level processor support #3785

Closed
vjsamuel opened this issue Mar 22, 2017 · 2 comments
Closed

Module/Prospector level processor support #3785

vjsamuel opened this issue Mar 22, 2017 · 2 comments

Comments

@vjsamuel
Copy link
Contributor

I understand that today we only support include_lines, exclude_lines, and exclude_files as processors at a prospector level and support filters at metricbeat module level where a user can provide any processor as a filter for the given module. This is a great feature to have in filebeat as well. Can the same be extended to filebeat where a user can say:

filters:
  - processor1
  - processor2

This is especially useful when custom processing needs to be done for specific log files. Putting them as global processors only slows down the pipeline as each and every log line needs to be verified.

@ruflin
Copy link
Member

ruflin commented Mar 22, 2017

We will also need this to better support the reloading feature. Currently it is not possible to add a new prospector and have a specific processor for it.

I remember we wanted to add this in the past but there was an issue that the event format on the processor level is not in the format the processor expects it. So it could be that some previous refactoring is needed.

@vjsamuel
Copy link
Contributor Author

not valid anymore :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants