Once a kernel event log file is generated and transferred to the development host (whether it's done automatically by the IDE or generated with tracelogger and imported into the IDE), you can then analyze the data using the System Profiler editor.
If you receive a Could not find target: Read timed out error while capturing data, it's possible that a CPU-intensive program running at a priority the same as or higher than qconn is preventing that agent from transferring data to the host system.
If this happens, restart qconn with the qconn_prio option set to a higher priority. You can use hogs or pidin to see which process is keeping the target busy and discover the process' priority.