-
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
Cherry-pick #19619 to 7.x: Init journald input #19782
Conversation
Pinging @elastic/integrations-services (Team:Services) |
❕ Build Aborted
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
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.
LGTM
Cherry-pick of PR #19619 to 7.x branch. Original message:
What does this PR do?
This changes introduces the journald input in filebeat based on the
input v2 API. Most of the reading and field transformation code is
shared with journalbeat
Integration tests are not yet implemented. I'd sugest to reimplement the existing journalbeat python tests in this package as more simple go based tests. Most of the reading and event transformation support is already shared with journalbeat, which gives us at least some confidence.
Note: this is just the input implementation. The API is not fully hooked up yet in Filebeat, which means that the input is not available to be configured yet.
Why is it important?
Provide journald input to the Agent
Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Configure input with
journald
type. The input settings match the ones currently found for journalbeat.Sample configuration:
use systemd-cat to write logs:
Related issues