Bug #59349 "First Seen" description in QUAN manual page misleading
Submitted: 7 Jan 2011 12:24 Modified: 2 Aug 2011 17:51
Reporter: Leandro Morgado Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Documentation Severity:S4 (Feature request)
Version: OS:Any
Assigned to: John Russell CPU Architecture:Any

[7 Jan 2011 12:24] Leandro Morgado
Description:
The MEM QUAN docs say:

"First Seen: The first time the query was seen within the given filter conditions."
 http://dev.mysql.com/doc/refman/5.1/en/mem-query-analyzer.html

This suggests that the "First Seen" time is affected by a time interval filter condition, however, that is not true. "First Seen" is the first ever time a "normalized" query was recorded. Here is an example:

===========================================
You ran this query in 2010-Aug-15 01:00:00 :

SELECT SLEEP(5);

And then you run this query on 2010-Jan-07 10:00:00:

SELECT SLEEP(123);

Then the normalized query is:

SELECT SLEEP();

The "First Seen" time for this query is always 2010-Aug-15 01:00:00. If you filter by all queries on Jan 07, you will see the normalized "SELECT SLEEP()" query. This happens because indeed this query was slow on Jan 07, but the first time it was seen is still Aug 15.

So in summary, the First Seen is not affected by the filter. It is always the value of the very first time the query was seen.
===========================================

How to repeat:
1) in the MEM Dashboard, go to the Query Analyzer tab

2) select a time interval so that you catch a normalized slow query that was "first seen" outside (in the past) of this time interval

3) See that "First Seen" value is previous to the time interval filter condition

Suggested fix:
Document this in all the MEM manuals, making it clear First Seen is not relative to the filter interval condition.
[2 Aug 2011 17:51] John Russell
Change has been made in both relevant places, in all 2.3 doc source branches.