-
Notifications
You must be signed in to change notification settings - Fork 419
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
[RFC] Remove process.ppid - Stage 0 #1337
Conversation
|
||
### Ingestion mechanisms | ||
|
||
APM, Beats, Elastic Agent, and any processors that populate `process.ppid` today will need to be identified and a migration plan to `process.parent.pid` established. |
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.
Will that a part of this RFC's process, or is that a separate effort?
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.
Separate effort; updating those data sources will happen outside the RFC process.
Here we're noting the Elastic data sources that may be impacted when the field is removed from ECS. As this RFC advances, we'll continue communicating that this change is coming, especially to the teams/areas most impacted. The teams can then plan and implement any necessary 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
Summary
Stage 0 proposal for deprecating and later removing the
process.ppid
field now that ECS also includesprocess.parent.pid
.Stage 0 (Strawperson) Criteria:
Preview of markdown proposal