PB-431: add saved search for S3 CloudTrail logs #46
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
|
@ckaenzig Thanks. If we need to make some fields searchable, instead of using a pipeline, we could as well try to add a custom mapping or alias fields in Elasticsearch. |
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.
Add a saved search for S3 logs, with a filter for pre-signed api calls (disabled by default).
The aws.cloudtrail integration uses
flattenedfields (JSON blocks) for several interesting query and response attributes, which don't seem to be really supported by Kibana. which limits the usefulness of a custom dashboard. The biggest issue is that the BucketName is in one of those fields.So this saved search is a start. If we need better visualizations, it looks like we'll need a custom pipeline which further parses the flattened fields into distinct attributes.