Cherry-pick #19659 to 7.x: Modified auditd ingest pipeline to handle node=hostname format #20526
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.
Cherry-pick of PR #19659 to 7.x branch. Original message:
What does this PR do?
This change permits auditd logs to be ingested whether or not they begin with a node=. Previous to this change a type= was expected.
It handles the case where name_format (man 5 auditd.conf) is a value other than none.
Also adding 10 lines of resulting audit log with name_format = hostname parameter on CentOS 7.
Why is it important?
When running auditd with name_format other than none, the log messages will begin with node= parameter rather than type=. This behavior caused such audit logs to fail ingestion. The use case for setting name_format would be with an audit server collecting audit logs from multiple hosts.
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas-~~ [ ] 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 in
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.~~