Hi David and Joe, many thanks for the feedback. I have thought a bit about this and I think I can craft pragmatic - but sufficiently clean - solution today. Maybe we can try to *evolve* this as a side-activity. I'll target v5-devel and above.
Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of [email protected] > Sent: Wednesday, September 08, 2010 7:04 PM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog stats - counters > > On Wed, 8 Sep 2010, Rainer Gerhards wrote: > > > I have thought once again about which counters I could provide > without > > generating most of the plumbing. Probably the only one I can envision > is the > > number of message objects inside the system (assuming that number of > queues > > itself and such is of really no interest at all), or more precisely > number of > > messages generated and number of messages deleted. This does roughly > reflect > > the number of messages processed, but only if no async queues are > used (they > > require some message duplication). If this is considered useful, I > could look > > into that. It probably takes two to three days to get that going with > some > > minimal plumbing for the background writer (done in a clean way). > > > > I could also output the main queue size, but once again be reminded > that this > > reflects only part of the picture (depending on config only a very > small > > part...). > > > > Feedback appreciated. > > I think that this would be useful to have. As it is, it's hard to tell > if > rsyslog is queuing messages or not, this would give you a tool to use > to > tell this. > > David Lang > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
