Closed vtoupet closed 1 year ago
Good catch! There were some exceptions from "requests" not handled as temporary network errors. Could you check if #76 (specifically 4fab5f3) will fix it?
Just for clarification: the library didn't crash really, it just logged the error, then put the log event back into the queue for the next attempt (and this repeats). So, you most probably did not loose any events, just the logging was very verbose.
I wanted to check how the behaviour when logstash server was down and a problem occurred (I am using gevent worker with gunicorn)
this is the gunicorn command line I am using:
the config is the following:
When the server is up again, logs are not sent (I suppose the reason is because of the above crash). FYI Other services (celery and other manage.py commands) work just fine.
app versions: