Dropped message count

Sorry for the activity, I hope this to be the last question - I've been playing with nxlog-ce for a week already.

How can I get a count of (unintentionally) dropped records? Something syslog-ng reports in "mark" messages... Do I have to create a buffer processor, drop the records "intentionally" in it and implement my own counter in script? Or does nxlog exhibit somehow its internal flow control stats?


AskedJanuary 10, 2016 - 7:24pm

Route path branching


please advise me how to configure the following setup:

  • several inputs (UDP, TCP, internal) joined into common path (i_udp, i_tcp, i_internal => p_pattern ...),
  • one global processor (pattern, filter)  module,
  • several outputs (file, UDP, TCP),
  • every message is delivered to one of outputs according to processor's decision.

I call it "route branching". The solutions I have come to so far:

AskedJanuary 10, 2016 - 7:17pm

Source code of community edition for community


will you, please, publish recent source code, the one the latest CE packages were built from? I made quite a few tests with 2.9.1504 on Debian and now would like to patch some minor problems of pm_pattern (and contributing back), but last published sources are 2.8.1248. And I can not get a changelog between theese two versions either (the changelog packaged in the binary package, as mentioned in the previous post, is too brief):

AskedJanuary 8, 2016 - 5:06pm

NXLOG 2.9.1504 New Features, Bug Fixes, Etc

Where can I find the NXLOG code history for the various releases? I am currently on NXLOG 2.9.1347 and need to know what's new and fixed in 2.9.1504 but cannot locate where this information is.

Thank You,

AskedJanuary 7, 2016 - 9:40pm