Enrico Tröger

The configuration looks good to me, I don't see an error. You could try adding a root logger with a console handler to check if there are any errors logged....

python-logstash-async logs any errors it encounters to STDERR if no specific logger is configured. So, either check the STDERR of your application for errors or configure a root logger as...

The lines just moved: the old line 305 is now at 308 (see the original at https://github.com/geany/plugins.geany.org/blob/f11c354f1302ab440793cafa3bd23a96de441b9b/gencontent.sh). The problem probably still exists under certain circumstances: ```shell enrico@endor:~$ [ -eq 0...

I would second the idea to include "published" and/or some aliases of it. Recently, I stumbled upon https://status.otc-service.com/rss/?mt=Europe%20%28Germany%29 which does not have a "guid" and the links in there are...

For me, `--bind-address` doesn't really make things better. I'm trying to run K3S also on a VPS and so do not want to expose to the rest of the world....

I experienced the same in a Kubernetes cluster. In my case the `clamd` process ran OOM and got killed by Kubernetes. I could solve it by increasing the memory limits...

> @eht16 maybe the health check issue is related to #380 and #369? @micahsnyder there is no health check issue for me, it works fine :D. Kubernetes does not support...

Would implementing this feature now being easier after 5.0? It's still desired to have a compact line based output and it would ease IDE integrations.

We could make it configurable more easily. The higher the `batch_size` is the more likely will be transmission errors, like timeouts or maybe processing errors on the Logstash side. While...

@cbeaujoin-stellar I implemented the new setting `QUEUED_EVENTS_BEATS_BATCH_SIZE` with a simple default. I think this is OK as the batch size is configurable and users can set it as they like.