MySQL Bugs: #35622: Rule scheduling error too ambiguous

Bug #35622	Rule scheduling error too ambiguous
Submitted:	27 Mar 2008 18:50	Modified:	9 Jan 2015 15:55
Reporter:	Kolbe Kegel	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S4 (Feature request)
Version:	1.3	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
When there is a problem scheduling a rule, the error issued is too ambiguous. This error occurs when trying to schedule a rule that relies on data collection items not available for the server version being monitored, for instance.

Here is an example of the error message:

An Error Occurred
U0059 There was a problem scheduling "Binary Log Usage Exceeding Disk Cache Memory Limits" against "myserver:3306".

How to repeat:
Try to schedule the "Binary Log Usage Exceeding Disk Cache Memory Limits" rule against a MySQL 4.0 server.

Suggested fix:
The error message should give more information.

It would be nice to know if the problem was related to:

o Server version
o Privileges given to the Agent user
o Some other problem

Even if it's not possible to identify which of these problems caused the error being shown, there should be a link to a resource that gives more information about the possible causes of the problem and some information about further troubleshooting that can be performed.

i'd like to see better error message on this as well (my 2 cents)

I don't believe we're going to fix this in 1.3

In 2.0, we are already passing along the error from the server for unsupported items. However, there appear to be some translation/substitution issues I need to investigate. For instance, we currently send up errors like:

"The server "{mysql}.{server}.{0013022597c80000.'127.0.0.1:3306'}" does not support item(s) "mysql.server.Binlog_Do_DB" required by monitor "17aa7ab7-cd22-4276-998d-e7ede9ab0dbc binary_logging_is_limited.name"."

Obviously the server name should be correctly substituted, the rule name should be substituted, "monitor" should be "rule" and there should be an associated error code. I'll work with Oldag and Eric on this.

Finally, other errors should include the error text as well as the generic "problem scheduling..." stuff.

I fixed this for the errors that I could. There's a couple of rules that throw a RuntimeException that I can't get the arguments or specific reasons for. I opened up a separate bug for that (36605)

I know more information was added to these errors in 2.0