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

[automation] update libbeat and beats packaging #7602

Merged
merged 3 commits into from
Mar 23, 2022
Merged

Conversation

apmmachine
Copy link
Contributor

What

Update with libbeat and beats packaging.

@apmmachine apmmachine added automation backport-skip Skip notification from the automated backport with mergify labels Mar 22, 2022
@apmmachine
Copy link
Contributor Author

apmmachine commented Mar 22, 2022

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /hey-apm : Run the hey-apm benchmark.

  • /package : Generate and publish the docker images.

  • /test windows : Build & tests on Windows.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@simitt
Copy link
Contributor

simitt commented Mar 22, 2022

Fleet container hasn't successfully started in the system tests - retriggering tests to see if it was a glitch or we have to further look into it.

@simitt
Copy link
Contributor

simitt commented Mar 22, 2022

/test

@axw
Copy link
Member

axw commented Mar 22, 2022

I've been waiting for elastic/beats#30805 to merge so I could backport #7488. That would explain why Fleet things aren't starting. I'll fix it now.

ph and others added 2 commits March 22, 2022 15:40
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
@simitt
Copy link
Contributor

simitt commented Mar 22, 2022

Yep, that backport has landed.

@axw
Copy link
Member

axw commented Mar 23, 2022

/test

@axw axw enabled auto-merge (squash) March 23, 2022 05:35
@axw axw merged commit 4396872 into 7.17 Mar 23, 2022
@axw axw deleted the update-beats-20220322033513 branch March 23, 2022 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation backport-skip Skip notification from the automated backport with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants