[MXS-3645] Make Transaction Performance Monitoring Filter non-experimental Created: 2021-06-23  Updated: 2021-10-20  Resolved: 2021-10-18

Status: Closed
Project: MariaDB MaxScale
Component/s: qlafilter
Affects Version/s: 2.5.13
Fix Version/s: 6.2.0

Type: New Feature Priority: Major
Reporter: Rob Schwyzer Assignee: Niclas Antti
Resolution: Fixed Votes: 0
Labels: None
Environment:

Ubuntu 18.05 LTS via MariaDB repository


Sprint: MXS-SPRINT-142

 Description   

A potential customer is highly interested in using https://mariadb.com/kb/en/mariadb-maxscale-25-transaction-performance-monitoring-filter/ but this is currently (despite docs not stating this) experimental only, which means it cannot be safely used in production.

The customer's specific statement for their interest in TPM is-

there was a goal of plotting query timings and providing some insight into transactions and the TPM looked to accomplish some of these goals

Customer also asked if this will be available properly in v2.6 (v6), but I am not seeing any roadmap for this feature nor inclusion on v6 release notes.

Can we consider taking steps necessary to make this prod-ready and to release it in an upcoming MaxScale version? If not, are there fundamental problems with the filter as-is and can we make a new feature which would address customer demand for the problems the TPM filter solves?



 Comments   
Comment by Manjot Singh (Inactive) [ 2021-07-15 ]

To clarify, this should be available in the default release. (toddstoffel can you get it in the next GA minor?)

Comment by Niclas Antti [ 2021-10-18 ]

The tpmfilter functionality has been moved to the qlafilter.

Generated at Thu Feb 08 04:22:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.