MySQL Bugs: #46171: MySQL audit log logged by MEM

Bug #46171	MySQL audit log logged by MEM
Submitted:	14 Jul 2009 14:48
Reporter:	Bogdan Kecman	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S4 (Feature request)
Version:	2.1	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
This is not really MEM issue as MySQL need to provide audit log first in order for MEM to be able to log / display it, but as the target feature request is to see the log via MEM dashboard..

It would be useful/needed/necessary to be able to see some of the "important" events from MySQL server via MEM
 - drop database
 - drop table
 - change config variables( like buffers for example)
 - create users 
 - grants
...

How to repeat:
.

Suggested fix:
first we need to make MySQL Server have auditing functionality, then we allow MEM to log/store/show it

There's another ticket somewhere for some of this but yes, it would be very nice if you can record for all mysql instances the:

- running config (SHOW VARIABLES)
- current grants (equivalent of mk-show-grants)

Then let the dba compare the values from one server to another.
Also ideally maintain all changes and thus also allow the values to be compared between different moments in time.

This makes later ensuring that servers are configured correctly much easier.
It also makes it easier to determine when a change was made and perhaps relate that to merlin performance changes.

Events like:
 - drop database / create database, drop table/create table events are notified to the dba, but are they easy to search for if you're are later trying to find out when something happened?

By the way there's no need for MySQL Server to have auditing functionality. If it does that would be great. This can be done now, by collecting state and then determining when changes take place and then being able to show them as needed.

With MySQL Enterprise Audit the completion of the request is one step closer.

I think this request should be used for audit logging and MEM.
Bug #34237 should be used for change management / logging.