Does "filebeat setup -e" need to be run every time I enable a module, or only once for all modules?

[andrew.klaassen]

So far I've been running "filebeat setup -e" every time I enable a new filebeat module. However, looking at its output, it seems to be setting stuff up for all of my modules, even the disabled ones.

Do I need to run "filebeat setup -e" every time I enable a new filebeat module, or only when I install it the first time or upgrade to a new version?

Thanks.

[stephenb (Stephen Brown)]

See this... (ha) I thought we answered this.

When/how often/from where does "filebeat setup -e" need to be run?

Hi @andrew.klaassen Yes, #3 is a pretty good strategy and I see it often used in larger / automated environmemtns. I think of this Filebeat Setup Host / Install. You should run setup whenever enabling a new module or when deploying a new version of filebeat across your landscape The version part is equally important as the templates, pipelines, dashboards can be updated, and templates and pipelines definitions include the version number. To be clear you do not need to run setup on every h…

@andrew.klaassen

Do I need to run "filebeat setup -e" every time I enable a new filebeat module, or only when I install it the first time or upgrade to a new version?

Yes, run setup when a new module and / or you change the version.

Yes some of all the assets are loaded when you run setup, but not all ... (which actually may have changed in 8.recent looks like 8.recent loads all the assets but that was NOT the behavior in 7.X as only the pipeline for enabled modules got loaded. )

I actually think we may be reducing/changing that behavior in the future so yes run setup with each new module to be safe..

So Yes run with each new module.

[andrew.klaassen]

Thanks. Yes, I see now that you did answer it already. I just got thrown off by the behaviour you're mentioning with recent 8 versions.

Thanks again!