Bug #50252 Order of Graph series is not always optimal for display
Submitted: 11 Jan 2010 20:02 Modified: 29 Jun 2010 17:15
Reporter: Jonathon Coombes Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Web Severity:S3 (Non-critical)
Version:2.1 OS:Any
Assigned to: Mark Leith CPU Architecture:Any
Tags: Graphs, mem, UI

[11 Jan 2010 20:02] Jonathon Coombes 
Description:
Some graphs in MEM do not draw the series in a way that makes them useful. That is, smaller series are written first and the large series is written over the top and makes the others unseen or mostly hidden.

Row Accesses is an obvious graph to see this issue.

How to repeat:
Examine certain graphs e.g. row accesses, and although there are 3 series listed, you can see only, or mostly, one series on the graph.

Suggested fix:
Look at drawing them in a different order, or changing how the graphs are done to allow better displaying of the information.
[28 Jun 2010 14:44] Enterprise Tools JIRA Robot 
Mark Leith writes: 
Patch pushed which splits out the Average Rows per Query series from the Row Accesses graph to it's own Row Access Statistics graph, in both 2.2 and trunk (2.3):

 359 Mark Leith	2010-06-28
     Bug#50252 / EM-3927 - Split the avg rows per query series from Row Accesses to its own graph

   added:
     src/silver/graphs/avg_row_accesses.xml
   modified:
     src/silver/graphs/resources_en.properties
     src/silver/graphs/resources_ja.utf8
     src/silver/graphs/row_accesses.xml