-
Notifications
You must be signed in to change notification settings - Fork 10
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 fileset for system module #55
Conversation
fixes #54 Beginning with release version 8 you need to give a fileset for "system" module of filebeat. Version 7 just used defaults. Since we are thinking about replacing modules by elastic agents and filebeat only without modules in special cases, I add a quick fix and flag it as experimental. Let's see how it works.
My initial diagnosis was wrong: https://discuss.elastic.co/t/filebeat-setup-exiting-module-system-is-configured-but-has-no-enabled-filesets/311584 . We just need to change the way we setup modules. Please note that #77 could make using modules in filebeat completely obsolete. Therefore I didn't put much effort in clean code for enabling modules. If we want to continue to support, we should find a better way than just running the same code over and over again. |
Default configuration with added modules will connect Filebeat to Logstash and then run Or, the most sophisticated solution: Make sure, Filebeat talks to Elasticsearch when doing |
0dd6a13
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me 👍
fixes #54
Beginning with release version 8 you need to give a fileset for "system" module of filebeat. Version 7 just used defaults.
Since we are thinking about replacing modules by elastic agents and filebeat only without modules in special cases, I add a quick fix and flag it as experimental. Let's see how it works.