MySQL Bugs: #46035: QUAN Query Popup still hard codes explain threshold

Bug #46035	QUAN Query Popup still hard codes explain threshold
Submitted:	8 Jul 2009 10:55	Modified:	28 Jul 2009 15:40
Reporter:	Mark Leith	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S3 (Non-critical)
Version:	2.1.0.1074	OS:	Any
Assigned to:	Josh Sled	CPU Architecture:	Any

Description:
The Explain Query tab for the QUAN popup still says:

"No EXPLAIN found (for performance reasons, EXPLAIN is only captured for queries that take longer than 500 ms)."

This is configurable now, and we should give those details here. 

How to repeat:
N/A

Suggested fix:
Describe how to configure the threshold per agent now

Josh Sled writes: 
revno: 7356
revision-id: jsled@asynchronous.org-20090716144830-yx5x60ec7mutfi74
parent: eric@mysql.com-20090716151921-nlyy8i24uas0xomt
committer: Josh Sled <jsled@asynchronous.org>
branch nick: local
timestamp: Thu 2009-07-16 10:48:30 -0400
message:
  EM-3427, Bug#46035: Move responsibility for creating the "no explain plan found, maybe because of ..." message to the Action.
  Factor out support code to determine quan config value variability amongst a server collection, for re-use by the QuanSummaryInfo.

Andy Bang writes: 
In build 2.1.0.1078

Marcos Palacios writes: 
Tested using build 2.1.0.1078.

The fix seems to have caused a side effect: On FF3 on OSX, for some queries, I get this error in the Firebug error console:

instanceData.returnedData.exampleQuery is undefined
   var haveExplainData = instanceDa...urnedData.exampleQuery.explain != null;\n

Marcos Palacios writes: 
Besides the above mentioned side effect, the fix for this bug is actually working: We see the threshold value depending on the db server. It also describes how to configure the threshold per agent.

Josh Sled writes: 
revno: 7375
revision-id: jsled@asynchronous.org-20090720174239-oe69w1it6xrbgdjh
parent: jsled@asynchronous.org-20090720173249-9y1oxughfrz3q9t2
committer: Josh Sled <jsled@asynchronous.org>
branch nick: local
timestamp: Mon 2009-07-20 13:42:39 -0400
message:
  EM-3427: fix javascript error introduced in previous fix

Marcos Palacios writes: 
Available in Build 2.1.0.1080.

Marcos Palacios writes: 
Verified fixed in build 2.1.0.1080.

Java script error does not show up.

Can you explain how to repeat this please so I can see exactly what the problem is. Thanks.

Diego Medina writes: 
Steps to reproduce it:

1- Enable query Analyzer (all 3 check boxes)
2- Set the Explain threshold on the Query Analyzer config popup toa high value, like, 1 min (to ensure you will not see an explain for simple queries.
3- Send some queries through the proxy port
4- Once you see the queries on the Query Analyzer tab, click on any of them
5- You will now see a message like"

No EXPLAIN plan found. For performance reasons, EXPLAIN plans are only captured for queries that take longer than the threshold configured for the server. For the server this query has been collected on, the threshold is 00:01:00.000.

Before, the threshold value on that popup was always 00:00:00.500 (the default value)

An entry was added to the 2.1.0 changelog:

When a query was clicked on the Query Analyzer page, the Explain Query tab displayed a potentially incorrect value for the Auto-Explain Threshold. The Threshold can actually be set to a user configurable value in Configure Query Analyzer, but the popup text did not reflect the currently set value, instead displaying a hard-coded default value.