MySQL Bugs: #48234: correlation graphs broken

Bug #48234	correlation graphs broken
Submitted:	22 Oct 2009 14:41	Modified:	6 Nov 2009 13:42
Reporter:	Josh Sled	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S2 (Serious)
Version:	2.2 alpha	OS:	Any
Assigned to:	Josh Sled	CPU Architecture:	Any

Description:
When selecting a time range on, say, a dashboard graph, the user will be taken to BrowseQueries, and he correct graph and graph-time-range will be selected.  However:

- the query time range will not agree with the graph time range.
- changes to the query range interval will not correctly update the graph or selection.
- changes to the graph type will not be updated correctly.

How to repeat:
see above

Suggested fix:
fix.

Josh Sled writes: 
revno: 7576
revision-id: jsled@asynchronous.org-20091022190734-3uz4fwwhvzrag50n
parent: jsled@asynchronous.org-20091022141218-h27ogvonwr11599h
committer: Josh Sled <jsled@asynchronous.org>
branch nick: local
timestamp: Thu 2009-10-22 15:07:34 -0400
message:
  EM-3670: hack in support for correlation graphs on BrowseQueries.

Keith Russell writes: 
Patch installed in versions => 2.2.0.1516.

Marcos Palacios writes: 
Verified fixed in service manager build 2.2.0.1517.

An entry has been added to the 2.2.0 changelog:

        When a time range was selected on a dashboard graph, the user
        was taken to BrowseQueries, and the correct graph and graph time
        range was selected. However, the following problems occurred:

            The query time range did not agree with the graph time
            range.

            Changes to the query range interval did not correctly update
            the graph or selection.

            Changes to the graph type were not updated correctly.