Bug #42082 Filtering of tracing for QUAN

Submitted:	13 Jan 2009 13:09
Reporter:	Johan Idrén	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S4 (Feature request)
Version:	2.0.0.7111	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	performance, quan

Description:
It should be possible to limit the queries that are being filtered/collected/analyzed by QUAN at the collection stage as well as it is currently in the presentation stage. 

How to repeat:
Enable QUAN, see that everything is recorded. Even stuff you have no interest in.

Suggested fix:
Add controls for filtering that affect the agent, not only presentation (similar to http://monitoringhost:18080/BrowseQueries.action would be great) to lessen the impact of collecting data or at least only collect specific data.

Flow would somehow be: 
Enter filtering requirement in web interface "Only record queries accessing table X"
Filtering string gets transferred to agent/proxy
Agent/proxy only records queries accessing table X

Other variants are of course User, Host, type of query (SELECT, DELETE) etc.

If the parsing isn't as slow as or slower than the collect-all method, then this should alleviate some of the performance hits in enabling QUAN.

Page generated in 0.037 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.