Show driver/application/user metadata in Query Profiler query summaries
It would be helpful if the Query Profiler showed the driver and user metadata associated with the connection over which a particular query was run.
After clicking on a particular plotted operation in the Query Profiler, the sidebar pops up and shows execution statistics and structure of the plotted op, but doesn't show anything about the driver/application/user that issued the command.
This query summary would be more actionable if the driver, driver version, application name, and user were also displayed in the query sidebar (these details may be recorded in a separate log entry from the command itself).
This information could then help pinpoint the source of the query so it can be adjusted if need be.
Marie
shared this idea
-
Ronny
commented
This will help us too a lot, especially filtering our the irrelevant Compass queries.
Ideally if you could have both exclude and include, this would be good. And extra points if you can filter on only the start of the string (as we also put version in appName). -
Karl
commented
3 years later and still an issue. Unfortunately, this renders the index suggestions largely useless for a busy database.
-
Evtim
commented
Using the profiler to narrow-down slow operations is great. One thing sorely missing is the ability to filter by "appName" - some of our top slow queries are from dev team working with compass or running experimental code vs the database as opposed to our main production app. We want to be able to ignore these when we perform the analysis - should be simple to implement as the metadata in the profile statistics already has a field with the desired information - "appName"