You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If profiling of SQL queries is enabled we could also track SQL queries and average time it took to execute them. The information is written to log_profiling under circumstances anyway. We'd just need a way to figure out which ones were already tracked and to make sure to not send queries that contain any private information (only queries that use bind parameters). We could check if there's a use of ? but still it could be the case that it is a mix of bound parameters and concatenated values...
It is not important but it would be kinda nice to see which queries are executed how often, how fast were they executed and especially to see a history of it.
Of course ideally there are monitoring tools used for such cases
The text was updated successfully, but these errors were encountered:
If profiling of SQL queries is enabled we could also track SQL queries and average time it took to execute them. The information is written to
log_profiling
under circumstances anyway. We'd just need a way to figure out which ones were already tracked and to make sure to not send queries that contain any private information (only queries that use bind parameters). We could check if there's a use of?
but still it could be the case that it is a mix of bound parameters and concatenated values...It is not important but it would be kinda nice to see which queries are executed how often, how fast were they executed and especially to see a history of it.
Of course ideally there are monitoring tools used for such cases
The text was updated successfully, but these errors were encountered: