Bug #40032 Agent still collects queries while the UI is set to quan=disabled
Submitted: 15 Oct 2008 1:33 Modified: 22 May 2009 13:50
Reporter: Diego Medina Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S2 (Serious)
Version:2.0.0.7075 OS:Any
Assigned to: Jan Kneschke CPU Architecture:Any
Tags: kay_merlin_time_permitting, mem_discuss_me

[15 Oct 2008 1:33] Diego Medina 
Description:
While we have the option to disable Query Analysis on the UI, the queries that go through the agent are still being collected.

Once you turn on Query Analysis on the UI, those queries show up on the UI.

How to repeat:
1- Install and start the agent and monitor
2- Go to the UI and disable Query Analysis by going to UI->Query Analysis
3- Click on "configure query analysis" on the top right and un-check all the boxes and click save
4- Send some queries through the agent (port 4040 by default)
5- Go to the UI and refresh the quan tab (wait about 5 minutes) and refresh again
You will not see any queries
6- Now, Turn query analysis on on the UI
7- Refresh the query analysis page and you will see the queries you sent a few minutes ago

Suggested fix:
The agent should respect the settings on the server
[13 May 2009 1:34] Gary Whizin 
see also #37819
[13 May 2009 8:17] Jan Kneschke 
A patch has been push with the work another bug:

1274 jan@mysql.com	2009-05-07
     replaced passive-quan-enable/disable by active, REST-based (mysql::quanconfig) 

       * added per-backend enable/disable 
       * removed passive auto-disable for QUAN data
       * added support for mysql::quanconfig
       * removed auto-config support (should be in admin instead)
       * disable QUANing by default

   modified:
     lib/quan.lua
     plugins/agent/items/quan.lua
[14 May 2009 2:29] Keith Russell 
Patch installed in versions => 2.1.0.1039.
[15 May 2009 3:19] Bill Weber 
verified fixed in agent build 2.1.0.1041
[22 May 2009 13:50] Tony Bedford 
An entry was added to the 2.1.0 changelog:

Even though Query Analysis was disabled through the user interface, the queries that go through the agent were still being collected.

When Query Analysis was turned back on in the user interface, those queries were then displayed.