[automation] update libbeat and beats packaging#7559
Merged
Conversation
Author
Member
|
/test |
This move the Manager.Start and Stop into the Beats' run method, this move ensure that the system is configured and ready to receive events. Having the Manager started and stopped at the Libbeat level was causing inconsistency when configuring the Beats by the Elastic Agent. The problem would lead to the following behavior: - Zombie Beats with only outputs configured - Beats without any inputs configured - Beats with some of the input configured. The problem was often cause by restarting the agent and having the machine under a significant load. See: elastic/beats#30694 for details
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Update with libbeat and beats packaging.