On Thu, 19 Apr 2012, Chris McCraw wrote:
On Thu, Apr 19, 2012 at 12:02 AM, Rainer Gerhards
<[email protected]> wrote:
But what I can say is that I have the strong feeling this will work for you.
I know at least of one datacenter which has a far higher data rate than you
have and they work very successfully with that feature. But YMMV: you need to
do some testing, which will identify potential bottlenecks, if there are any.
I am thrilled to do testing and can even do some in production, but
I'm not sure how to be sure no messages are dropped. Any suggestions
for trackable high-load-generation? I've been using logger and/or nc
in a loop from the command line to log "# rather long message..."
where # increases sequentially to be sure no messages were dropped,
but the production log stream is just a bunch of http requests and I
don't have any gauge of when one doesn't make it through, so
real-world testing might not be informative.
what I've done in the past is use tcpdump to capture a bunch of real
syslog data, then used tcpreplay to play it back at whatever rate I want
(and since I know how much data was captured, I can compare it to the
resulting logs)
a little better than just a scripted test, and it can work to higher data
rates.
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
