CODEWITHSUNDEEP
phpmysqllogginglamp
Cranio
Cranio

Reputation: 9847

Query logging scenarios in query-heavy website

I'm facing with the problem of logging the database activity of a LAMP (Debian/PHP/MySQL) site.

This is complicated by the fact that I'd wish every query logged also with the user's context in which they were launched, to know, let's say, "who did what". I admit to be not too well informed about MySQL's logging capabilities but I have problems in finding info about my specific scenario.

Now we have implemented a mysql_query() replacement (I know, I know, code rewriting with PDO and prepared statements is on its way!) that executes the query and logs it with INSERT DELAYED in a log table.

Problem is, the log table, as one can easily predict, reaches millions of rows, of which the oldest ones are quite useless. Other problem is, for every query needed, two are executed. A partial solution has been NOT to log the SELECTs.

Another solution would be logging on text file with fancy log rotation and gzipping and stuff. But how about knowing the user context in which the queries were run?

Has someone implemented a successful query logger that logs also the logged user and is performance-aware?

Upvotes: 1

Views: 133

Answers (1)

Petah
Petah

Reputation: 46060

Well its a trade off. If you want to log user activity it will take up lots of space, and use more processing.

I personally log all HTTP requests for PHP files (including GET, POST, COOKIE, etc), instead of SQL queries. But that still leads to millions of rows. I also keep them forever as HDD space is generally cheap. When I need to do audits, it can be slow, but I don't need to audit often.

Writing to a file would just make it harder to analyse, and you will still be processing extra IO every request.

If space is an issue, you could just run a cron job to remove all rows older the X amount of time.

Upvotes: 2

Related Questions