-
Notifications
You must be signed in to change notification settings - Fork 19
Add memfd_create
fields to process datastream
#564
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
Conversation
Is this PR meant to add or change any data stream mappings? Then you would also make changes in other folders.
If the field(s) we are looking at do need to be mapped, then they should be added above. If the field is part of ECS (~8.10) then just adding the field name to the above data stream should be enough. If the field is part of a newer ECS release, then we may need to do some bookkeeping to update our ECS reference. If the field is not part of ECS (a pretty common case, for our workflow here), then the field definition goes in So then in But again, if we don't need to search on it, you do not have to map. Depends on the end use case here. if this is just getting that EAF error message to go away, then you might be done already.
|
It is rendered in the doc directory right next to the src directory. It looks like the tool to do that rendering was run already for this PR. |
@pzl thanks for you help. So, as far as I'm aware these aren't ECS fields, so it sounds like the changes also need to go in Is the info in |
so if these do need mapping for filtering/search, then yes, put the details about the fields in Yes, |
@pzl Does that look right? |
@fearful-symmetry stellar. Looks perfect. If you could add your sample values for |
@pzl I think we need a code owner review? |
Needs a review from someone on |
The memfd object/flags aren't in ECS but this stage0 RFC proposal (so still early/might be revised when aligning with OTEL) was merged which adds |
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.
duplicate entry in one doc file, otherwise LGTM!
@fearful-symmetry FYI this is likely going to have to be backed out. A prerelease package version just went out, and kibana CI is failing with:
The recent merge of #555 into Looking at the error, I think there is a simple fix here. It should be Absolutely fascinating that this wasn't caught in the |
@pzl ack! Sorry about that! Yeah, weird that CI didn't catch that... |
Change Summary
This is part of https://github.com/elastic/endpoint-dev/pull/15318, as we need to update the fields here in order for the EAF tests to pass.
The documentation here is a tad difficult so this is probably incomplete; I'm not sure what the difference is between
custom_schemas
andcustom_documentation
, and if I should just copy-and-paste fields between them?Sample values
Sample document:
Release Target
Q/A
For mapping changes:
make
after making the schema changes, and committed all changesmetadata
change, I also updated both transform destination schemas to match