Hi David, On Thu, 2008-12-18 at 21:38 -0800, [email protected] wrote: > with messages appearing out-of-order the 'last message repeated X times' > is pretty useless.
Not really. Please note that form the perspective of the output module, messages do not appear out of order. The output module receives a stream of messages, and the "last message repeated x times" logic works on that stream. So no matter if messages are re-ordered by async queues (or UDP or whatever), the "last ... times" correctly reflects the way things were handed to the output module. But I concur that this feature, in its current state, is very questionable. I've talked about this on the mailing list quite some time, I think there is also at least one blog post about it. > > I think I remember reading about an option to disable this, but another > work-around to the problem is to change the output so that it becomes > 'last message repeated X times %msg%', so you can see (most, if not all) > of the message being repeated in the line telling you that it was > repeated. As I said, the message in front of this message is either another repeat message or the message that is being repeated. So you can always trace back to what was repeated (but it is painful). Given the feedback I received on this feature (use cases), it should probably (and v4 would be an appropriate version to do so) be redisigned to be a rate-limiting feature on the input side. That would pretty much simplify code, too. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
