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

Filebeat Setup Command #215

Open
devinmatte opened this issue Jun 21, 2019 · 2 comments
Open

Filebeat Setup Command #215

devinmatte opened this issue Jun 21, 2019 · 2 comments

Comments

@devinmatte
Copy link

I've noticed that after enrolling devices through puppet with filebeat, filebeat is present, the config is correct, but it doesn't start sending up logs until I have run filebeat setup manually.

Is it supposed to be run as a part of the plugin, is it intentional that it doesn't, or can a flag be added to run that as part of the install process?

@pcfens
Copy link
Owner

pcfens commented Jul 8, 2019

Is that for sending logs to elasticsearch? The module doesn't setup the structure in ES, but as I understand it, that should be a one time step for a single node (we don't send directly to ES, so I might be off on this part).

@freibuis
Copy link
Contributor

filebeat setup is useless if you are using other systems like graylog. I would suggest looking at it from your storage side to make sure the types are installed or
run filebeat setup once if

  • adding new filebeat modules
  • a procotcol/module version has changed.
  • sending logs to a newly provisioned elastic search service

I find it better to add the filebeat setup to the elastic search install manifiest as a post install process
but that means you will need to install filebeat on to that elastic search node

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

No branches or pull requests

3 participants