EQL: consistent naming for event type vs event category #53073
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
Pinging @elastic/es-search (:Search/EQL) |
Contributor
|
Excited about these changes. I'll work on syncing up the existing docs to match the new field name + defaults. Thanks @aleksmaus. |
Contributor
|
@elasticmachine run elasticsearch-ci/default-distro |
aleksmaus
added a commit
to aleksmaus/elasticsearch
that referenced
this pull request
Mar 4, 2020
aleksmaus
added a commit
that referenced
this pull request
Mar 4, 2020
jrodewig
added a commit
that referenced
this pull request
Mar 4, 2020
Updates the documented default `event_category_field` and `timestamp_field` values for the EQL search API. Also updates related guidance in the EQL requirement docs. Relates to #53073.
jrodewig
added a commit
that referenced
this pull request
Mar 4, 2020
Updates the documented default `event_category_field` and `timestamp_field` values for the EQL search API. Also updates related guidance in the EQL requirement docs. Relates to #53073.
jrodewig
added a commit
that referenced
this pull request
Mar 5, 2020
* [DOCS] Document `any` keyword in EQL syntax Adds documentation for the `any` keyword to the EQL syntax docs. Includes: * Definition of an event type and its relationship to the event type field. * Example matching all event types using `any` keyword * Example matching event types beginning with a digit * Example using `any` with `where true` * Remove references to `event_type_field` default * Reuse "Events starting with digits" section * Updates for #53073
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #52941