Introduction

Event tracking services are a group of services that allow implementor to monitor various database activities. Two main actors involved are:

Producers: Those who emit one or more events
Consumers: Those who are interesting in processing events generated by consumers

Following services are part of this groups of services.

Events related to user authentication (s_mysql_event_tracking_authentication)
Events related to COM command execution (s_mysql_event_tracking_command)
Events related to a session connection (s_mysql_event_tracking_connection)
Events related to execution status (s_mysql_event_tracking_general)
Events related to global variable access (s_mysql_event_tracking_global_variable)
Events related to program lifecycle (s_mysql_event_tracking_lifecycle)
Events to emit special message to log (s_mysql_event_tracking_message)
Events to perform query rewrite (s_mysql_event_tracking_parse)
Events to track query execution (s_mysql_event_tracking_query)
Events to track stored program execution (s_mysql_event_tracking_stored_program)
Events to track table access (s_mysql_event_tracking_table_access)

When a consumer component is installed, it registeres its interest in receiving notification for any subset of events by implementing corresponding services.

A producer, as a part of generating an event will inform all consumers who have registered interest of a given event.

Through some of the above mentioned events, a consumer can indicate producer to either generate an error/warning or stop the execution or both.

server component, which is part of MySQL server is one example of producer component. At different point of execution, it emits events of all classes of events mentioned above.

Please take a look at following pages for more details: