The README doesn't explain how lumberjack would be better than, say, rsyslog. about logstash-forwarder HOT 5 CLOSED

Both rsyslog and syslog-ng perform poorly in my experience. Both bloat memory over time as well as being CPU hogs at moderate load.

Regarding features (and not bugs), lumberjack aims to have reliable log transport. syslog-ng doesn't have this, but rsyslog does in the form of RELP. However, RELP appears to not have compression available.

lumberjack aims to use a few megs of memory at worst, and actually enforces this with setrlimit() on startup.

I'll fill in more details about lumberjack in its README once the project is ready for general consumption. Early adopters welcome, but it's still in heavy experimentation.

from logstash-forwarder.

Oh, and with respect to "better than X" - I doubt I'll explain lumberjack in this way. I'm likely only to describe the features (and why those features exist). Comparing against other projects is out of scope for this document.

from logstash-forwarder.

I'm also confused by the lack of information in the README. Is this meant to be compatible with logstash? Could you use a lumberjack client and logstash server?

from logstash-forwarder.

how about now? https://github.com/jordansissel/lumberjack#use-with-logstash

from logstash-forwarder.

@jordansissel great, thanks!

from logstash-forwarder.