-
Notifications
You must be signed in to change notification settings - Fork 431
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
Introduce process.executable. #209
Conversation
There are a few places in Beats that will need changed because we have
|
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.
@andrewkroh To understand what this means from a migration perspective:
- Are these 1-1 mappings that change from 6.x to 7.x? Meaning we could add an alias in 6.x to the renamed field?
- Any other changes?
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.
@ruflin Yeah these would be one-to-one mappings. I think we have a process.exe
in 6.x that can be mapped with an alias. And one of my open Packetbeat PRs has a uses process.exe
as a new field so that can be updated now.
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.
Ok, as it's only 1-1 mappings I'm good in moving forward with this. Will need a rebase.
Rebased. |
Also move the more canonical process fields to the top.
Note that in this PR, I also take the opportunity to move the more important
fields to the top. You may want to review one commit at a time.