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

Cherry-pick #9994 to 6.x: Do not stop collecting events when journal entries change #10485

Merged
merged 8 commits into from
Feb 4, 2019

Conversation

kvch
Copy link
Contributor

@kvch kvch commented Feb 1, 2019

Cherry-pick of PR #9994 to 6.x branch. Original message:

Previously sd_journal_wait was not used. From now on all changes to journals are detected.

I also added custom seccomp policy to Journalbeat.

Closes #9533

Previously sd_journal_wait was not used. From now on all changes to journals are detected.

I also added custom seccomp policy to Journalbeat.

Closes elastic#9533
(cherry picked from commit cead4b6)
@kvch kvch force-pushed the backport_9994_6.x branch from 7c0280a to 9db33a4 Compare February 1, 2019 13:58
@urso
Copy link

urso commented Feb 4, 2019

beats-ci faliure is unrelated to this change.

@kvch kvch merged commit fbc9dcc into elastic:6.x Feb 4, 2019
@mictsi
Copy link

mictsi commented Feb 13, 2019

Does this commit solve #9994 ? If yes is it possible to update the packages in your repost for apt/rpm?

The current packages have a binary with the following version:
journalbeat version 6.6.0 (amd64), libbeat 6.6.0 [2c385a0 built 2019-01-24 10:35:01 +0000 UTC]

DStape pushed a commit to DStape/beats that referenced this pull request Aug 20, 2019
…ournal entries change (elastic#10485)

Cherry-pick of PR elastic#9994 to 6.x branch. Original message:

Previously sd_journal_wait was not used. From now on all changes to journals are detected.

I also added custom seccomp policy to Journalbeat.

Closes elastic#9533
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants