-
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
Update ECS in auditbeat sessionmd processor #38994
Conversation
The sessionmd processor requires the latest process field from ECS, so this updates the ECS fields to the latest version, which has the required fields.
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Remove duplicate process fields that exist in the base `fields.ecs.yml`, and remove some other fields that are not used in sessionmd.
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
Proposed commit message
The sessionmd processor requires some of the latest process field from ECS, that are not currently in libbeat. This adds the required ECS field assets to the processor.
Without these fields, some field types would be incorrect. For example,
session_leader.start
should be date, but were sent as keyword.Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
To verify this, build auditbeat, and run
auditbeat export template
and verify the template is correct. In particular, verify that process hassession_leader
,entry_leader
, andgroup_leader
, and thatstart
andend
have type "date".How to test this PR locally
Related issues