-
Notifications
You must be signed in to change notification settings - Fork 215
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
s3 input is not separating log entries #420
Labels
Comments
@tfmm didi u find any solution? |
Not yet, but I haven't been looking into it recently.
…On Mon, Aug 7, 2023, 10:48 valentinacala ***@***.***> wrote:
@tfmm <https://github.com/tfmm> didi u find any solution?
—
Reply to this email directly, view it on GitHub
<#420 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUP2GRMZDEIEFI2JSIFLYLXUD55HANCNFSM6AAAAAAW4BTYNU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Using s3 input from cloudwatch logs (gzipped json) to send to opensearch, and all entries from each log file in s3 are being put into one entry in opensearch.
To Reproduce
Setup fluentd using below config, with proper permissions on s3 and sqs.
Expected behavior
Each log entry should be parsed into separate entries in opensearch.
Your Environment
Your Configuration
Your Error Log
Additional context
No response
The text was updated successfully, but these errors were encountered: