On Wed, Oct 16, 2013 at 5:51 PM, Rainer Gerhards <[email protected]>wrote:
> > On Wed, Sep 18, 2013 at 7:45 PM, Radu Gheorghe > <[email protected]>wrote:- > failed.es counter doesn't seem to work. I mean, at least not for JSON > >> errors, which was the easiest way to poke it. I also tried a slightly >> smarter hack of making ES think the message field is numeric, to cry a >> NumberFormatException when it finds out it's a string. Sadly, >> failed.esremained 0. Anyway, here's how I did that: >> > > I still need to look into that but thought it is better to least fix the > other one ;) > > I'll keep you posted. If you would llike to give the new version a try, > that would be great. > OK, I couldn't stand it and had another look. It seems that only failures in batch mode were counted. If so, I have fixed this now. Please note that this counter does not count messages but actully failure occurences. I thought about message couting, but that's more performance intense, so probably not something we want to do (at least by default). This is documented in the stats counter description now. I did *not* these fixes other than by compiling -- due to lack of readily available environment. So feedback would be most appreciated. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
