On Mon, 29 Nov 2010, Hajo Locke wrote:
read article on http://www.rsyslog.com/doc/rsyslog_high_database_rate.html
is there a possibility to find out queuelength of unwritten messages to see
if it is still growing?
i try to use rsyslog for my smtp-cluster but iam unexperienced how fast my
system is writing data.
if i could see a kind of number of stored messages it would help to assess
current situation.
historically there has not been a good way to find this. This was
asked for a month or two ago, but I'm not sure if it got in or not.
One thing you can do is to watch how much ram rsyslog is using, if the
queue is continuing to grow, the amount of ram used will grow. However, I
do not think it always releases memory when the queue size goes down.
btw, is it possible to write with usual syslog to a rsyslogserver? or should
rsyslog be used for client and server?
rsyslog is happy to accept messages from a normal syslog sender. depending
on what features you want, there may be advantages to useing rsyslog as
the sender as well.
1. software consistancy (you don't have to worry about two different
syslog apps)
2. you can use different log formats (high precision timestamps, etc)
3. you can use different transport mechanisms (relp, tcp, encrypted, etc)
but in no way do you have to change the senders when you change the
receiver.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
