Skip to content
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

Add a new readme section for reserved top level field sets #257

Merged
merged 2 commits into from
Dec 10, 2018

Conversation

webmat
Copy link
Contributor

@webmat webmat commented Dec 7, 2018

No description provided.

Copy link
Contributor

@MikePaquette MikePaquette left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@webmat
Copy link
Contributor Author

webmat commented Dec 7, 2018

Thanks! I'll wait for @ruflin to see it next Monday before I merge.

@webmat webmat self-assigned this Dec 7, 2018
ECS does not define the following field sets yet, but the following are expected
in the future. Please avoid using them:

- `match.*`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is new to me :-)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's the result of vulnerability or threat detection. That's how the "match" is recorded (e.g. what field name matched, what time the detection occurred, etc.)

@webmat webmat merged commit a91e314 into elastic:master Dec 10, 2018
@webmat webmat deleted the reserved-words branch December 10, 2018 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants