Log in

No account? Create an account
entries friends calendar profile My Website Previous Previous Next Next
Mark Atwood
And another Drizzle plugin interface, for error messages
MySQL, and thus currently Drizzle, logs stuff to it's error log. "Stuff" being errors, warnings, and info messages. Inside the code, they ultimately get sent to stderr, which is directed to whatever file is specified by the "log-error" option. It's all in the MySQL documentation at http://dev.mysql.com/doc/refman/6.0/en/error-log.html

I'm changing that in Drizzle, replacing the error logging stuff with a plugin interface.

The first implementation will, just like the current builtin system, write to a file, or to stderr. I expect soon after, plugins that send the messages to syslog, as SNMP traps, and to a CSV table, will be written.

Just like the query logging work, getting this going will shink the drizzle core even more, and likely remove still more unneeded locks.

Tags: ,

3 comments or Leave a comment
From: atcurtis Date: October 5th, 2008 04:26 pm (UTC) (Link)

error logging

Believe it or not, I already had a plugin interface implemented for MySQL which did this more than a year ago, originally implemented by Brian's request.
You're welcome to the code, they can be found by searching though the commit emails at lists.mysql.com - I had implemented logging to syslog, Windows event logger and even logging to any table (although logging to transactional tables wasn't recommended because the rows inserted would be rolled back if the main transaction was rolled back).

krow From: krow Date: October 6th, 2008 07:14 am (UTC) (Link)

Re: error logging

This is pretty much similar to what you did (though we have session now so it makes it a bit easier).

We need to work out a few things around calling objects in the server from plugins but the rest is moving along nicely.
From: mike503 Date: October 5th, 2008 11:22 pm (UTC) (Link)
syslog FTW
3 comments or Leave a comment