-
Notifications
You must be signed in to change notification settings - Fork 449
Advance RFC 0049 (entity store) to stage 2 #2537
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
This advanced RFC 0049 to stage 2, and adds entity fields to the ECS schema as beta fields.
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
@mjwolf did you try altering the subsets file to allow this? I'm pretty sure that's how we allow the complex nested re-use ie client.user.group. I think you just need to add entity to the user.target section https://github.com/elastic/ecs/blob/main/schemas/subsets/main.yml#L600 |
Using the subsets file, add entity under target, for the fieldsets which use this. For `host`, entity is not nested under target, as it doesn't have this field. This matches the requirments of the RFC.
50c963b to
85d733d
Compare
c502759 to
68e8f31
Compare
Advance RFC 0049 (entity store) to stage 2
1. What does this PR do?
This advanced RFC 0049 to stage 2, and adds entity fields to the ECS schema as beta fields.
2. Which ECS fields are affected/introduced?
This adds new
entityfields as beta, and modifies host, user, cloud and service fieldset by adding entity fields to them through re-use.3. Why is this change necessary?
This advanced RFC 0049 through the RFC process, and makes the entity fields part of the ECS schema, which will unlock use cases using these fields.
4. Have you added/updated documentation?
YES
5. Have you built ECS and committed any newly generated files?
YES
6. Have you run the ECS validation tests locally?
YES
7. Anything else for the reviewers?
Commit Message
Advance RFC 0049 (entity store) to stage 2