Hi,
I was hoping that someone with experience using the MySQL output
module, or maybe someone familiar with the source, could help me
understand a few details about the module.
1) Can ommysql use SSL connections to the database server? If not, are
there any future plans to add SSL support?
2) Do failover destinations ('$ActionExecOnlyWhenPreviousIsSuspended',
http://wiki.rsyslog.com/index.php/FailoverSyslogServer) work correctly
with ommysql? If so, how and when do connection failures
register--does the failover happen when the MySQL client fails to
execute an INSERT statement, or when the TCP socket dies, or what?
3) Does ommysql support periodically re-connection to the database server?
4) Is the retry limit for ommysql's INSERT process configurable? The
HOWTO (http://www.rsyslog.com/doc-rsyslog_mysql.html), in the section
'On Reliability...', says "If rsyslogd is unable to store a message,
it performs one retry." I assume this means the retry limit is
hard-coded--is that right?
5) How efficient is ommysql in comparison to omtcp or omrelp? I
imagine there's more overhead for the MySQL protocol, but I don't know
whether are other considerations, too. I would love to hear what
levels of load people experience, with ommysql in production, and what
kind of log volumes they handle.
Thanks!
Ryan B. Lynch
[email protected]
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
