[Filebeat] Change field type in aws cloudtrail fileset to flattened #19020
Conversation
This file contains 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
leehinman
added
enhancement
Filebeat
botelastic
bot
added
the
needs_team
|
Pinging @elastic/siem (Team:SIEM) |
botelastic
bot
removed
the
needs_team
A string representation of the following fields was stored and indexed as keyword. Changing to a flattened object which is more easily searched. - request_parameters - response_elements - additional_eventdata - service_event_details Closes elastic#18866
leehinman
force-pushed
the
18866_cloudtrail_flattened
branch
from
1a47edc to
f004955
Compare
adriansr
reviewed
Jun 9, 2020
| @@ -21,9 +22,6 @@ | |||
| "fileset.name": "cloudtrail", | |||
| "input.type": "log", | |||
| "log.offset": 0, | |||
| "related.user": [ | |||
There was a problem hiding this comment.
related.user is lost after this change, but can't see why it happens. Can it be fixed?
5 tasks
andrewkroh
removed
the
needs_backport
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
A string representation of the following fields was stored and indexed
as keyword. Changing to a flattened object.
Why is it important?
Changing to flattened object makes searching easier and avoids mapping explosion
Checklist
- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
Related issues