Bug #41643 Please provide statistics on error return state in query analyzer
Submitted: 19 Dec 2008 15:27 Modified: 24 May 2010 13:42
Reporter: Simon Mudd (OCA) Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Web Severity:S4 (Feature request)
Version: OS:Any
Assigned to: CPU Architecture:Any

[19 Dec 2008 15:27] Simon Mudd
Current query analyzer functionality does not allow you to see if any of the normalised queries have returned an error.

It's not possible to search for queries by error state (normally where an error exists, or a specific error)
It's not possible to see what percentage of a normalised query generated errors (you hope it's 0%)
If any errors are produced the statistics should be adjusted to not take these samples into account. (this may be done already).

When multiple servers are being searched you may expect to get some errors coming from the application due to misconfiguration, old versions of the client software being installed, or other reaasons and currently it's not possible to isolate this type of problem.

It would be handy if this were possible.

How to repeat:

Suggested fix:
Provide search facilities based on one or more error states.
Show in the pop-up windows statistics of number of queries and number of queries with and without errors and perhaps even number of different errors.
[7 May 2010 16:02] Enterprise Tools JIRA Robot
Mark Leith writes: 
This was resolved in 2.1.0.
[24 May 2010 13:42] MC Brown
A note has been added to the 2.2.0 changelog: 

        The Query Analyzer interface has been improved to show more                                                                                        
        information about query states and for the filtering system to                                                                                     
        enable you to view and filter the contents to more easily                                                                                          
        identify problem queries.   For more information, see <xref linkend="mem-query-analyzer-filtering"/>.