-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Load configuration from modules.d when running setup subcommand #12340
Conversation
4a536de
to
6d22781
Compare
6d22781
to
03a3388
Compare
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.
Thanks for fixing this! We have been removing the convert_timezones
conditions from the pipeline templates (#12253), but I guess we should continue supporting templates in pipelines for other cases by now.
Co-Authored-By: Jaime Soriano Pastor <jaime.soriano@elastic.co>
Codecov Report
@@ Coverage Diff @@
## master #12340 +/- ##
==========================================
- Coverage 58.02% 57.8% -0.23%
==========================================
Files 933 934 +1
Lines 57454 57485 +31
==========================================
- Hits 33340 33231 -109
- Misses 21050 21192 +142
+ Partials 3064 3062 -2
Continue to review full report at Codecov.
|
…tic#12340) Previously, when running the subcommand `setup`, configuration from `modules.d` was not loaded. This lead to Filebeat ignoring settings of modules which had special template directive in their pipelines. Thus, uploading incorrect pipelines. Now when running setup configuration from the modules folder are read and pipelines are loaded. Closes elastic#9747
@kvch as this is marked as a bug in CHANGELOG, can you backport it to 7.2? Or is there a reason not to? |
No reason. Backporting it. |
…tic#12340) Previously, when running the subcommand `setup`, configuration from `modules.d` was not loaded. This lead to Filebeat ignoring settings of modules which had special template directive in their pipelines. Thus, uploading incorrect pipelines. Now when running setup configuration from the modules folder are read and pipelines are loaded. Closes elastic#9747 (cherry picked from commit 5d7c1fa)
…tic#12340) Previously, when running the subcommand `setup`, configuration from `modules.d` was not loaded. This lead to Filebeat ignoring settings of modules which had special template directive in their pipelines. Thus, uploading incorrect pipelines. Now when running setup configuration from the modules folder are read and pipelines are loaded. Closes elastic#9747 (cherry picked from commit 5d7c1fa)
…ing setup subcommand (#12941) * Load configuration from modules.d when running setup subcommand (#12340) Previously, when running the subcommand `setup`, configuration from `modules.d` was not loaded. This lead to Filebeat ignoring settings of modules which had special template directive in their pipelines. Thus, uploading incorrect pipelines. Now when running setup configuration from the modules folder are read and pipelines are loaded. Closes #9747 (cherry picked from commit 5d7c1fa) * add missing function to libbeat/beat/beat.py
…en running setup subcommand (elastic#12941) * Load configuration from modules.d when running setup subcommand (elastic#12340) Previously, when running the subcommand `setup`, configuration from `modules.d` was not loaded. This lead to Filebeat ignoring settings of modules which had special template directive in their pipelines. Thus, uploading incorrect pipelines. Now when running setup configuration from the modules folder are read and pipelines are loaded. Closes elastic#9747 (cherry picked from commit 8f27fe8) * add missing function to libbeat/beat/beat.py
Previously, when running the subcommand
setup
, configuration frommodules.d
was not loaded. This lead to Filebeat ignoring settings of the modulesystem
and loading incorrect pipelines.Now when running setup configuration from the modules folder are read and pipelines are loaded.
TODO
Closes #9747