-
Notifications
You must be signed in to change notification settings - Fork 26
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
Kinesis put record error #50
Comments
@rgsriram Thanks for reporting! I think this happens whenever the underlying beat is unable to produce valid events for your logs. So, my best bet is you need to fix your log format somehow. To see what's causing the issue, you can enable debug logs so awsbeat dumps relevant events and records that helps further investigating the cause. Line 90 in 5b58657
|
You can add an command-line flag |
Thanks for the reply.
…On Sun, Jan 6, 2019 at 11:46 AM KUOKA Yusuke ***@***.***> wrote:
You can add an command-line flag -d '*' to the beat to enable debug
logging.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#50 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGvZR7r_tTrSMe4hY8CunVDRrXUA6P0mks5vAZTIgaJpZM4YSK8n>
.
--
*Sriram G*
*Tech*
|
Shouldn't it be agnostic on message format? Filebeat does not care what it is shipping if it is ascii files. |
my debug log looks like this
|
I seem to be getting the same error.. |
I solved this with a clue from the metricbeat.yml file in the project repo..
|
I am keep getting this error.
streams/client.go:97 retrying 5 events on error: failed to put records: InvalidParameter: 1 validation error(s) found. minimum field size of 1, PutRecordsInput.Records
Below is my filebeat.yml file. I couldn't figure out what is the error.
`
The text was updated successfully, but these errors were encountered: