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.