On Sep 7, 2010, at 11:11 AM, Aaron Wiebe wrote: > On Tue, Sep 7, 2010 at 2:07 PM, <[email protected]> wrote: >> >> 1. stats that are cheap to gather, generate >> examples current length of queues, age of oldest message in each queue, >> number of messages processed (possibly even per output) >> 2. stats that are expensive to gather or generate >> examples: average length of queues, average time to process messages > > Expensive stats shouldn't be the responsibility of rsyslog though - > trending over time and the like should be the responsibility of a > third party product (ie, cacti/mrtg). As long as the stats are easily > made available through snmp or other methods, the trending should be > done outside rsyslog. >
Agreed, rsyslog should just report the current stats and any trending/analysis should be done externally. No different than running iostat or other tools. One other timing stat I would love to see is the amount of time in each step of the pipeline (time to read the message from the socket, time processing it through any rules, time spent in any queues, time spent writing to disk, etc). Haproxy has a good example of this in it's logging (8.2.3. HTTP log format - http://haproxy.1wt.eu/download/1.4/doc/configuration.txt). -Joe Name: Joseph A. Williams Email: [email protected] Blog: http://www.joeandmotorboat.com/ Twitter: http://twitter.com/williamsjoe _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
