We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are users seeing this error message or similar when using s3 input:
handleSQSMessage failed: json unmarshal sqs message body failed: invalid character 'd' in literal false (expecting 'a')
2020-08-26T10:05:10.780Z ERROR [s3] s3/input.go:257 handleSQSMessage failed: json unmarshal sqs message body failed: invalid character 'e' in literal true (expecting 'r')
This issue is to track the process on fixing this issue.
Discuss forum issues: https://discuss.elastic.co/t/s3-filebeat-input-cloudfront-logs-handlesqsmessage-failed-json-unmarshal-sqs-message-body-failed/239716 https://discuss.elastic.co/t/s3-filebeat-input-error/246654
The text was updated successfully, but these errors were encountered:
Pinging @elastic/integrations-platforms (Team:Platforms)
Sorry, something went wrong.
kaiyan-sheng
No branches or pull requests
There are users seeing this error message or similar when using s3 input:
This issue is to track the process on fixing this issue.
Discuss forum issues:
https://discuss.elastic.co/t/s3-filebeat-input-cloudfront-logs-handlesqsmessage-failed-json-unmarshal-sqs-message-body-failed/239716
https://discuss.elastic.co/t/s3-filebeat-input-error/246654
The text was updated successfully, but these errors were encountered: