I would look at these options:
A) Write an audit plugin that filters events based on username.
For simplicity, the username can be hardcoded in the plugin itself, or for elegance, it can be configured using the plugin variable if this problem persists.
See http://dev.mysql.com/doc/refman/5.5/en/writing-audit-plugins.html
B) Examine the -init-connect server option.
For example, call the stored procedure, check the value of user () / current_user (), and write the trace to the log (insert into the table) if a connection with the user is detected.
See http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysvar_init_connect
This is probably the closest to the connection trigger.
C) Use the performance schematic toolkit.
This assumes 5.6.
Use the performance_schema.setup_instrument table to enable hardware only. Use the performance_schema.setup_actors table only for tool sessions for this user.
Then, after the system has been running for a while, look at the activity for this user in the following tables:
- the performance_schema.users table will tell you if there was any activity at all
- table performance_schema.events_statements_history_long will show the last completed queries
- the performance_schema.events_statements_summary_by_user table will show aggregated statistics about each type of statement (SELECT, INSERT, ...) performed by this user.
Assuming you have a user defined as "old_app" @ '%', a likely subsequent question would be to find out where (which host (s)) this old application is still connecting to.
performance_schema.accounts will simply show that: if traffic for this user is visible, it will show each user @hostname the source of the traffic. Statistics are also aggregated by account, look for tables% _by_account%.
See http://dev.mysql.com/doc/refman/5.6/en/performance-schema.html