-
Notifications
You must be signed in to change notification settings - Fork 46
Dropping lots of messages #5
Comments
A couple of things to try:
|
Thanks much.
I'll see what verbose logstash has to say. Seems like teaching the lambda script about aggregated logs might be worthwhile. |
You can also check out the stats that KPL is producing for you. Look in the Custom Metrics namespace of CloudWatch. You can check if the number of records that it delivered matches up with how many you were expecting. |
Nothing notable in the logstash verbose output. Looking at the logs from lambda itself, I see a number of Will look at the metrics next. |
Looks like this is something related to the lambda I'm trying to execute (https://github.com/awslabs/amazon-elasticsearch-lambda-samples/blob/master/src/kinesis_lambda_es.js). I switched to the ES bulk API and things started behaving as desired. Don't believe this is an issue with your project. Thanks again for the help. |
Hey @csakoda - did you end up sorting things out? |
Yup, just pushed a few million events over night to test it out :) Thanks again. |
Good to hear!! |
I am testing a simple setup of
logstash-forwarder -> logstash -> kinesis -> lambda -> ES
I can get individual messages to flow through without issue.
However when logstash-forwarder goes to batch lines (say submit 10 log lines at once), I only see some or none of the lines in ES. I found that disabling aggregation helped some (when True no batched messages were appearing in ES at all)
I'm not seeing any errors in the logstash output, or in my lambda function. Anyone have insights?
The text was updated successfully, but these errors were encountered: