thinking back to the testing of the v5 code that I have been doing this last week, one thing that would be very useful is if there is a way to find out what the current queue lengths are.
one possible way to do this would be to have rsyslog watch for a signal and when it receives it, spit out the queue stats. for the stats definantly the length of each queue, possibly timestamps of oldest and newest message in each queue when spitting them out, some possible approaches are to stderr pro: simple con: stderr may not appear if rsyslog is running as a daemon from startup add a log message to the main queue containing the data pro: still fairly simple con: if there is a long queue, or it is blocked the data may not be visable for a while have each queue walker thread generate a message internally and process it pro: the data will show up fast, through the normal log mechanism con: this is probably the most work to imeplement this is not a critical issue, but it could be something that would speed up development in the long run by making it easier to figure out the state of the system. or I could have just missed how something like this is already supported ;-) David Lang _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
