Assume that you have SQL Server Analysis Services (SSAS) installed on Microsoft SQL Server 2016 or 2017. When you run an SSAS Profiler trace to trace Query Cube Begin and Query Cube End events, the ConnectionID and SPID values are not retrieved. However, you can see the values in a SSAS 2014 Profiler trace.
Note Even XEvents cannot capture the values.
SSAS 2016 Profiler screen shot
SSAS 2014 Profiler screen shot
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.