Events stored in the DB is sent before about python-logstash-async HOT 4 CLOSED

Yes but I think we can't do much here with the TCP transport. Logstash does not respond in any way to the messages sent, so we never know if they were processed sucessfully. This is a limitation of the TCP input in Logstash, not of this library.

Your workaround seems sensible to me, maybe it's worth to report this to Logstash. It should be possible to open the TCP input in Logstash first when it is also capable of processing events.

Another alternative would be to use the Beats transport (https://python-logstash-async.readthedocs.io/en/stable/config.html#options-for-configuring-the-log-handler), recently added in python-logstash-async, as with the Beats protocol, Logstash will acknowledge the received events.

from python-logstash-async.

Another workaround could be to do a 10-15 second timeout after connection before starting to sending logs too. Not sure if thats a wanted design choice to do, though.

I'll look into the Beats transport, thank you.

from python-logstash-async.

I really don't want to add an arbitrary timeout before sending to Logstash.
IMO the problem is on the Logstash side and adding such quirks doesn't make it better.

from python-logstash-async.

Beats worked like a charm like you said, thank you.

from python-logstash-async.