On Wed, 6 Apr 2016, Daniel Ellis wrote:
size is how many items are in the queue at the time it reports the data,
Since this is just after pstats adds all it's logs to the queue, this is
going to start at the number of items pstats reports and go up if there are
more messages pending.
I see, sounds like that's what I'm looking for.
you can add a name= field in an action() statement and that name will be
reported instead of the action number. with even a few of these you can
identify the other actions relative to the named ones.
Perfect!
This is missing a lot of fields that I'm used to seeing, how old a version
of rsyslog are you using?
I'm on 7.4.4, the version that ships with Ubuntu 14.04. I recognize that I
could upgrade to the newer package, but I'm trying to work with and test on
the version we're using in production, which can't be upgraded as easily.
That's something you need to think about. 7.4 is pretty old at this point
(current is 8.17), and the new versions are available in a repo (directly from
adiscon as a PPA, and I think much more recent versions are in backports)
Basically, I'm trying to reproduce the failure case of what happens when a
central rsyslog server starts backing up, causing the clients shipping to
it to queue, causing local writes to block and slow down the application.
I just found that I had different behavior in my network in the case of the
central server not keeping up vs the central server being unreachable, so test
both cases.
David Lang
_______________________________________________
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.
