Max SQL Queries Per Transaction
This parameter will appear only if the ADVANCED SETTINGS flag is set to ‘true’. Typically, from the detailed diagnosis of a slow/stalled/error transaction on a JVM node, you can drill down to view the SQL queries (if any) executed by that transaction from that node and the execution time of each query. By default, eG picks the first 500 SQL queries executed by the transaction, compares the execution time of each query with the SQL EXECUTION CUTOFF configured for this test, and displays only those queries with an execution time that is higher than the configured cutoff. This is why, the MAX SQL QUERIES PER TRANSACTION parameter is set to 500 by default.
To improve agent performance, you may want the SQL EXECUTION CUTOFF to be compared with the execution time of a less number of queries – say, 200 queries. Similary, to increase the probability of capturing more number of long-running queries, you may want the SQL EXECUTION CUTOFF to be compared with the execution time of a large number of queries – say, 1000 queries. For this, you just need to modify the MAX SQL QUERIES PER TRANSACTION specification to suit your purpose.