-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Unable to use Filebeat service due to hard-coded default. #280535
Comments
Same issue here, I tried to get it working with I copied the service, renamed If anyone has a solution how to clear the default value please tell us :) |
@roberth is that intended behavior? What do we miss? |
@SuperSandro2000 |
Then it is a breaking change. Sometimes it is unavoidable. We just need to make sure to add a release notes entry. |
Actually, no idea how I could oversee this in the first place. But it's possible to disable the output using I am going to continue working on #322425 to improve the documentation of the module for the option search. |
Describe the bug
The Filebeat service definition has a hardcoded default of an output to an elasticsearch instance on localhost. If I want to have a filebeat output to logstash, however, the Filebeat service only supports one output and with my configured output and the default, the service will not start.
Steps To Reproduce
Steps to reproduce the behavior:
A configuration of:
Generates the following file:
and a config of
generates a config of
Neither is a config that Filebeats will accept with an error of
Exiting: error unpacking config data: more than one namespace configured accessing 'output' (source:'/var/lib/filebeat/filebeat.yml')
Expected behavior
There shouldn't be a default so that a valid config file can be generated with an output other than ElasticSearch
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.The text was updated successfully, but these errors were encountered: