Bug #28145 NMAS reports excessive table scanning, indexes not being used with little help.
Submitted: 27 Apr 2007 20:34 Modified: 26 Aug 2010 9:24
Reporter: Morgan Tocker Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Advisors/Rules Severity:S4 (Feature request)
Version: OS:Any
Assigned to: CPU Architecture:Any

[27 Apr 2007 20:34] Morgan Tocker 
Description:
The alerts include  "excessive table scan" , "index not being used efficiently".

These are not always so effective because they will not show the offending query (or queries around the time of the offending query) at the time of the alert from the slow query log or show processlist.

How to repeat:
* Install MySQL
* Install NMAS
* Observe
[28 Apr 2007 17:45] Valeriy Kravchuk 
Thank you for a problem report. I think, this is a reasonable feature request, but not a bug. I am not sure that it is always only one offending query (easy to find) that leads to these alerts.
[26 Aug 2010 9:24] Mark Leith 
This is resolved in MEM 2.2. These alerts now give you a link to Query Analyzer, filtering for any query that has the no_index_used / no_good_index_used flags (via the MySQL protocol) set to TRUE. 

That is, QUAN now identifies, with an icon in the overview, every single statement that does a full scan / doesn't use an index.