-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Cherry-pick #19962 to 7.x: [Filebeat] Fix s3 input parsing json file without expand_event_list_from_field #20134
Conversation
Pinging @elastic/integrations-platforms (Team:Platforms) |
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
--------------------- >> end captured stdout << ----------------------
--------------------- >> end captured stdout << ----------------------
--------------------- >> end captured stdout << ----------------------
--------------------- >> end captured stdout << ----------------------
--------------------- >> end captured stdout << ----------------------
--------------------- >> end captured stdout << ----------------------
--------------------- >> end captured stdout << ----------------------
--------------------- >> end captured stdout << ----------------------
--------------------- >> end captured stdout << ----------------------
--------------------- >> end captured stdout << ---------------------- Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
CI failure is not related. |
Cherry-pick of PR #19962 to 7.x branch. Original message:
What does this PR do?
This PR is to fix s3 input when parsing json files without
expand_event_list_from_field
config parameter.During testing I found
offset
is not working properly for s3 input events, this PR also fix it.Why is it important?
For some logs, such as Cloudflare, json looks like:
instead of with a head field like:
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Create a test log file:
Gzip the log file:
Upload the file to S3 bucket and add property:
or manually upload this file to s3 bucket and change the property there.
Change filebeat input to s3 in
filebeat.yml
Run
./filebeat -e
Related issues