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

Clarify documentation around reloading configs #5676

Closed
ppf2 opened this issue Nov 21, 2017 · 1 comment
Closed

Clarify documentation around reloading configs #5676

ppf2 opened this issue Nov 21, 2017 · 1 comment
Assignees
Labels

Comments

@ppf2
Copy link
Member

ppf2 commented Nov 21, 2017

For users who land on this page directly https://www.elastic.co/guide/en/beats/filebeat/6.0/_live_reloading.html via search or google search on reloading, it will be helpful to clarify that live reloading only works on externally configured files (https://www.elastic.co/guide/en/beats/filebeat/6.0/filebeat-configuration-reloading.html#filebeat-configuration-reloading) and does not work on the main filebeat config file (eg. /etc/filebeat/filebeat.yml) itself.

Also, we are beginning to see users who are switching from a single filebeat config file into multiple ones to make use of the reloading feature, except that it is common for copy and paste to end up producing something like the following:

filebeat.prospectors:
  - type: log
... and so on

Instead of the expected

  - type: log
... and so on

It will be helpful to create a warning box on this page (https://www.elastic.co/guide/en/beats/filebeat/6.0/filebeat-configuration-reloading.html) to remind the users that the definitions in these externally config files must start with -type: always without the filebeat.prospectors: or filebeat.modules lines.

@dedemorton
Copy link
Contributor

Closing because this was fixed in #6046

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

No branches or pull requests

2 participants