Maxscale filter error question

Hello, we are testing both maxscale versions 2.2.21 and 2.3.20. The DB is auroramysql, and maxscale uses auroramon. Moving from version 5.7 to version 8, an issue occurred due to a change in the name of the transcation parameter, so regex_filter was applied. Most of the time it works fine, but occasionally an error occurs because the filter fails to replace. The log in the filter is No match tx_isolation.*: [SELECT @@tx_isolation] : Routed [COM_QUERY] to SELECT @@tx_isolation It says that tx_isolation cannot be matched. It seems that errors are occurring intermittently because the filter does not match properly. Is there a way to resolve the issue when upgrading the DB version from mysql version 5.7 to version 8 without applying the filter? This is our filter content. ex) [filter] type=filter module=regexfilter match=tx_isolation.* replace=transaction_isolation log_file=/test/filter.log options=ignorecase log_trace=true