Hi all, I have a few questions about the impstats module, the output it's generating, and queues in general.
I'm seeing this in my stats output: Apr 6 03:44:44 rsyslog-client rsyslogd-pstats: main Q: size=15 > enqueued=202 full=0 discarded.full=0 discarded.nf=0 maxqsize=16 > This post <http://www.rsyslog.com/how-to-use-impstats/> explains most of the fields, but what exactly is "size". As I understand it, the default main message queue size is 10,000. I've also tried explicitly setting this, but the "size" output still says 15. My goal here was to test queueing as well as whether I would be able to monitor the queues on the sender if they got too large. I tried an experiment where I turned off the receiving server (receiving via relp). Here was the pstats output before turning off the server: Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: imuxsock: submitted=106 ratelimit.discarded=0 ratelimit.numratelimiter s=102 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 1: processed=0 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 2: processed=0 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 4: processed=1 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 5: processed=250 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 6: processed=0 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 7: processed=0 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 8: processed=0 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 9: processed=0 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 10: processed=0 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 11: processed=0 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 12: processed=0 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 13: processed=249 failed=249 *Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 14: processed=251 failed=0* Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: action 15: processed=0 failed=0 Apr 6 03:48:44 rsyslog-client rsyslogd-pstats: main Q: size=15 enqueued=266 full=0 discarded.full=0 discarded.nf=0 ma xqsize=16 And here was the output after 1) turning off the server, and 2) sending 100 messages: Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: imuxsock: submitted=207 ratelimit.discarded=0 ratelimit.numratelimiters=202 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 1: processed=0 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 2: processed=0 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 4: processed=1 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 5: processed=366 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 6: processed=0 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 7: processed=0 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 8: processed=0 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 9: processed=0 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 10: processed=0 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 11: processed=0 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 12: processed=0 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 13: processed=365 failed=365 *Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 14: processed=367 failed=99* Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: action 15: processed=0 failed=0 Apr 6 03:49:44 rsyslog-client rsyslogd-pstats: main Q: size=15 enqueued=382 full=0 discarded.full=0 discarded.nf=0 maxqsize=16 I assumed that the purpose of the queue was to allow messages to back up in the case of unforeseen connectivity issues, but in this case, all of the messages appear to just have dropped, and the maxqsize hasn't incremented at all. Is my understanding fundamentally wrong here? Additionally, is it possible to identify *which* action is associated with an action number? In this case, I originally thought my relp action was #5 until I tried the failure scenario and saw it was actually #14. Thanks for any help anyone can offer. _______________________________________________ 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.
