Bug #51035 Notification about errors in agent log
Submitted: 9 Feb 2010 17:17 Modified: 9 Jan 2015 10:33
Reporter: Andrii Nikitin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S4 (Feature request)
Version:2.1.0.1096 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[9 Feb 2010 17:17] Andrii Nikitin 
Description:
It will be useful if notification is sent when error occurs in agent log.

How to repeat:
Real life agent logs may be full of different error messages, so it is important to troubleshoot them immediately. E.g.:

2010-02-03 01:24:19: (critical) proxy-plugin.c.1539: Cannot connect, all backends are down.
2010-02-04 13:58:52: (critical) (share/mysql-proxy/quan.lua:815) auto-EXPLAIN for 'bbf0b4b6724ce88d0a7384ffddf71dcd' failed with: 1064
2010-02-05 07:57:48: (critical) exception received from server: Internal error: jdbc:mysql://mc01mon-02:4040/mem?createDatabaseIfNotExist=true&...

Suggested fix:
E.g. create collection item called "error_in_agent_log" and update it whenever important error message is logged.
[11 Feb 2010 13:02] Simon Mudd 
Also in the mysqld.log log-error