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 CloudFront Standard Log Parser #4

Merged
merged 15 commits into from
Mar 30, 2021

Conversation

mashiike
Copy link
Contributor

What is this PR

Currently, only jsonl S3 objects can be routed.
However, there was a usecase where I wanted to route CloudFront's Standard Log.
Furthermore, after routing, I would like to read the log using Redshift Spectrum or Athena.
Therefore, it is a little convenient if the S3 object after routing is in JSONL format.

@mashiike mashiike requested a review from fujiwara March 25, 2021 07:42
README.md Outdated
@@ -38,6 +38,8 @@ $ s3-object-router \
Usage of s3-object-router:
-bucket string
destination S3 bucket name
-convert-json-record
convert the record to JSON format. use if -parser when not "json"
Copy link
Contributor

Choose a reason for hiding this comment

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

-format (json|none) (default none) is better I think. For example, enable to add -format parquet in feature.

@mashiike mashiike requested a review from fujiwara March 29, 2021 10:38
Copy link
Contributor

@fujiwara fujiwara left a comment

Choose a reason for hiding this comment

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

👍

@fujiwara fujiwara merged commit 6ea2c00 into master Mar 30, 2021
@mashiike mashiike deleted the feature/add-parser-flag-for-cloudfront-log branch March 30, 2021 05:50
@mashiike
Copy link
Contributor Author

🍿 🎊

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.

2 participants