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.

Sign up for GitHub

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

Jump to bottom

Central management: When we remove all the inputs for a beat it still keep the original configuration. #9010

Closed
ph opened this issue Nov 9, 2018 · 1 comment · Fixed by #9023
Closed

Central management: When we remove all the inputs for a beat it still keep the original configuration. #9010

ph opened this issue Nov 9, 2018 · 1 comment · Fixed by #9023
Assignees
@exekias
Labels
bug libbeat

Comments

@ph
Copy link
Contributor

ph commented Nov 9, 2018 •
edited
Loading

Steps to reproduce:

  1. Create a tag input with a log input and watch /var/log/*/log
  2. Create a tag output with an output to ES.
  3. Apply both tags to a beat.
  4. Wait until the beats ingest some documents.
  5. Remove both tags from the beats.

Current Behavior
The beat still keep reading and sending events to ES

Expected behavior:
Beats is going back to sleep and stop any inputs and outputs.

NOTES: Modules also have the same issue as the input.
@ph ph added the libbeat label Nov 9, 2018
@ph ph added the bug label Nov 9, 2018
@ph
Copy link
Contributor Author

ph commented Nov 9, 2018

Same problem with Metricbeat

@exekias exekias mentioned this issue Nov 9, 2018
Merged
exekias pushed a commit to exekias/beats that referenced this issue Nov 12, 2018
Unset existing config blocks when they are missing
0484f3c 
When a configuration block type (ie output) is not set in Central
Management, Kibana doesn't return it in the payload.

Before this change, Beats was not taking that into account os missing
block types were not reloaded in case they changed. In particular that
means that if an output configuration exists and is removed, Beats won't
apply that change.

This PR fixes that behavior by detecting missing types and applying nil
config to them.

Fixes elastic#9010
exekias added a commit that referenced this issue Nov 12, 2018
@exekias
Unset existing config blocks when they are missing (#9023)
f805d6c 
* Unset existing config blocks when they are missing

When a configuration block type (ie output) is not set in Central
Management, Kibana doesn't return it in the payload.

Before this change, Beats was not taking that into account os missing
block types were not reloaded in case they changed. In particular that
means that if an output configuration exists and is removed, Beats won't
apply that change.

This PR fixes that behavior by detecting missing types and applying nil
config to them.

Fixes #9010
exekias added a commit to exekias/beats that referenced this issue Nov 12, 2018
@exekias
Unset existing config blocks when they are missing (elastic#9023)
2be00f5 
* Unset existing config blocks when they are missing

When a configuration block type (ie output) is not set in Central
Management, Kibana doesn't return it in the payload.

Before this change, Beats was not taking that into account os missing
block types were not reloaded in case they changed. In particular that
means that if an output configuration exists and is removed, Beats won't
apply that change.

This PR fixes that behavior by detecting missing types and applying nil
config to them.

Fixes elastic#9010

(cherry picked from commit f805d6c)
@exekias exekias mentioned this issue Nov 12, 2018
Merged
exekias added a commit to exekias/beats that referenced this issue Nov 12, 2018
@exekias
Unset existing config blocks when they are missing (elastic#9023)
8ae1bba 
* Unset existing config blocks when they are missing

When a configuration block type (ie output) is not set in Central
Management, Kibana doesn't return it in the payload.

Before this change, Beats was not taking that into account os missing
block types were not reloaded in case they changed. In particular that
means that if an output configuration exists and is removed, Beats won't
apply that change.

This PR fixes that behavior by detecting missing types and applying nil
config to them.

Fixes elastic#9010

(cherry picked from commit f805d6c)
@exekias exekias mentioned this issue Nov 12, 2018
Merged
exekias added a commit that referenced this issue Nov 12, 2018
@exekias
Unset existing config blocks when they are missing (#9023) (#9042)
fd45e59 
* Unset existing config blocks when they are missing

When a configuration block type (ie output) is not set in Central
Management, Kibana doesn't return it in the payload.

Before this change, Beats was not taking that into account os missing
block types were not reloaded in case they changed. In particular that
means that if an output configuration exists and is removed, Beats won't
apply that change.

This PR fixes that behavior by detecting missing types and applying nil
config to them.

Fixes #9010

(cherry picked from commit f805d6c)
exekias added a commit that referenced this issue Nov 12, 2018
@exekias
Unset existing config blocks when they are missing (#9023) (#9041)
2274afe 
* Unset existing config blocks when they are missing

When a configuration block type (ie output) is not set in Central
Management, Kibana doesn't return it in the payload.

Before this change, Beats was not taking that into account os missing
block types were not reloaded in case they changed. In particular that
means that if an output configuration exists and is removed, Beats won't
apply that change.

This PR fixes that behavior by detecting missing types and applying nil
config to them.

Fixes #9010

(cherry picked from commit f805d6c)
leweafan pushed a commit to leweafan/beats that referenced this issue Apr 28, 2023
@exekias
Unset existing config blocks when they are missing (elastic#9023) (el…
4799960 
…astic#9042)

* Unset existing config blocks when they are missing

When a configuration block type (ie output) is not set in Central
Management, Kibana doesn't return it in the payload.

Before this change, Beats was not taking that into account os missing
block types were not reloaded in case they changed. In particular that
means that if an output configuration exists and is removed, Beats won't
apply that change.

This PR fixes that behavior by detecting missing types and applying nil
config to them.

Fixes elastic#9010

(cherry picked from commit 5410b93)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@exekias exekias

Labels
bug libbeat
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Unset existing config blocks when they are missing exekias/beats
2 participants
@ph @exekias