WARNING - ConnectionBus_Queries: Query executed in ... - Suggestion
Hello everyone ;)
I have an idea or a suggestion related to the logs "WARNING - ConnectionBus_Queries: Query executed inWARNING - ConnectionBus_Queries: Query executed in ... "
I think it would be quite cool and very much useful to get in these logs the exact place in the app where this located. By the exact place I mean, the page / widget ( more specific always better ) or the exact retrieve action. Maybe if it would log the XPATH and not only the SQL generated query it would be a great improvement. Then I can easily identify the exact place and I can start optimizing it faster.
Furthermore I would rely less and less on additional tools like APD & NanoProfiler.
Also, please let me know if there's an alternative or an easier way to do this in case I am missing it.
Thank you!
Agreed Marcian, the warning is great but the massive SQL is hard to pinpoint exactly what went wrong. For a small app you can sort of understand what it's trying to do but for a larger one it becomes a nightmare.
I can understand it's recording this at the db level and is separate to the rest of the app so I can understand why it's like this but it isn't that useful.
I think the real solution Mendix is trying to implement is with Tracing. This should allow you to monitor your requests / microflows in a lot more detail to determine long running actions. I've had good success with it locally and now trying to get it working for targeted troubleshooting for deployed envs....
Here is an image with what I mean. I would like to see the exact source of these generated SQLs. So I can point to the problem easier and fix it.