[Filebeat] Add text & flattened fields in aws cloudtrail fileset#19121
Merged
leehinman merged 1 commit intoelastic:masterfrom Jul 9, 2020
Merged
Conversation
Contributor
|
Pinging @elastic/siem (Team:SIEM) |
6018c95 to
ee10c64
Compare
Contributor
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
13f9645 to
dbdb87c
Compare
Contributor
Author
|
run tests |
0faa7fb to
575a038
Compare
AWS cloudtrail events have the following fields where the subfields are highley variable: requestParameters, responseElements, additionalEventData and serviceEventDetails. multi_fields added to following fields - aws.cloudtrail.request_parameters - aws.cloudtrail.response_elements - aws.cloudtrail.additiona_eventdata - aws.cloudtrail.service_event_details flattened version of the fields are stored here: - aws.cloudtrail.flattened.request_parameters - aws.cloudtrail.flattened.response_elements - aws.cloudtrail.flattened.additiona_eventdata - aws.cloudtrail.flattened.service_event_details Closes elastic#18866
575a038 to
cf0ec3d
Compare
Merged
5 tasks
leehinman
added a commit
to leehinman/beats
that referenced
this pull request
Jul 10, 2020
AWS cloudtrail events have the following fields where the subfields are highley variable: requestParameters, responseElements, additionalEventData and serviceEventDetails. multi_fields added to following fields - aws.cloudtrail.request_parameters - aws.cloudtrail.response_elements - aws.cloudtrail.additiona_eventdata - aws.cloudtrail.service_event_details flattened version of the fields are stored here: - aws.cloudtrail.flattened.request_parameters - aws.cloudtrail.flattened.response_elements - aws.cloudtrail.flattened.additiona_eventdata - aws.cloudtrail.flattened.service_event_details Closes elastic#18866 (cherry picked from commit d16ecc9)
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jul 13, 2020
* upstream/master: Add text & flattened fields in aws cloudtrail fileset (elastic#19121)
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jul 13, 2020
* upstream/master: Fix parsing timestamp in Filebeat registry tests (elastic#19796) Add text & flattened fields in aws cloudtrail fileset (elastic#19121)
v1v
added a commit
to v1v/beats
that referenced
this pull request
Jul 13, 2020
* upstream/master: [CI] support windows-2012 (elastic#19773) Do not update go.mod during packaging and testing (elastic#19823) Fix typo in ILM warning message (elastic#19819) [Winlogbeat] Remove beta tag from Powershell and Security modules (elastic#19817) feat: move the multibranch pipeline job to the beats repo (elastic#19698) Fix parsing timestamp in Filebeat registry tests (elastic#19796) Add text & flattened fields in aws cloudtrail fileset (elastic#19121)
leehinman
added a commit
that referenced
this pull request
Jul 13, 2020
AWS cloudtrail events have the following fields where the subfields are highley variable: requestParameters, responseElements, additionalEventData and serviceEventDetails. multi_fields added to following fields - aws.cloudtrail.request_parameters - aws.cloudtrail.response_elements - aws.cloudtrail.additiona_eventdata - aws.cloudtrail.service_event_details flattened version of the fields are stored here: - aws.cloudtrail.flattened.request_parameters - aws.cloudtrail.flattened.response_elements - aws.cloudtrail.flattened.additiona_eventdata - aws.cloudtrail.flattened.service_event_details Closes #18866 (cherry picked from commit d16ecc9)
melchiormoulin
pushed a commit
to melchiormoulin/beats
that referenced
this pull request
Oct 14, 2020
AWS cloudtrail events have the following fields where the subfields are highley variable: requestParameters, responseElements, additionalEventData and serviceEventDetails. multi_fields added to following fields - aws.cloudtrail.request_parameters - aws.cloudtrail.response_elements - aws.cloudtrail.additiona_eventdata - aws.cloudtrail.service_event_details flattened version of the fields are stored here: - aws.cloudtrail.flattened.request_parameters - aws.cloudtrail.flattened.response_elements - aws.cloudtrail.flattened.additiona_eventdata - aws.cloudtrail.flattened.service_event_details Closes elastic#18866
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
What does this PR do?
AWS cloudtrail events have the following fields where the subfields
are highley variable: requestParameters, responseElements,
additionalEventData and serviceEventDetails. This PR adds a text
multi_field to the existing fields and adds a new flattened field.
multi_fields added to following fields:
flattened version of the fields are stored here:
Why is it important?
The string representation of the highly variable subfields wasn't
meeting everyones needs. The text multi field and flattened objects
should make searching on these fields much easier.
Checklist
- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
Related issues