I think the ExecutionLog3 view is an exceptionally good feature! However I don't understand why is ItemPath field allowed to be NULL. When I query the View. I see a lot of times where an item with NULL itempath has taken lot of processing, render and data fetch time. but pity there is no way to know who that item was because ItemPath is null. MSDNStudent Knows not much!

Typically the itempath is null for ad-hoc executions (when Source=Adhoc) meaning that it is either a dynamically generated report model based drillthrough report, or a Report Builder report that is previewed on a client (using the run button in RB)

Makes sense. because in both cases of adhoc query and a fresh report being developed in report builder, there is no ItemPath because perhaps the item is not saved yet. MSDNStudent Knows not much!