Extended events trace missing data...

• jmetape

  Right there with Babe

  Points: 734

  More actions

  October 2, 2018 at 12:29 pm

  #415758

  Hi, I'm setting up a process to monitor our SSAS Queries using extended events.The xmla to start the trace is below. I put the xmla in a SSAS DDL task in SSIS. I'm experiencing two different behaviors when the trace is started from my local machine vs when it is started from a job (as our service account). In both cases the trace starts, however  when executed from a job (as our service account) some of the fields are not populated. 

  here is a screenshot of the  trace results when the trace is started locally, note the highlighted columns are populated and RequestID has a number in it:
  

  here are  the results when the trace is created as the service account . The highlighted columns are not populated and RequestID are all 0's:

  

  Here is the xmla that is starting the trace:
  <Create xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
  <ObjectDefinition>
    <Trace>
    <ID>SSASQueries</ID>
    <Name>SSASQueries</Name>
    <AutoRestart>true</AutoRestart>
    <XEvent xmlns="http://schemas.microsoft.com/analysisservices/2011/engine/300/300">
     <event_session name="TraceQuery" dispatchLatency="0" maxEventSize="0" maxMemory="4" memoryPartition="none" eventRetentionMode="AllowSingleEventLoss" trackCausality="true" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
      <event package="AS" name="QueryEnd" />
      <target package="package0" name="event_file">
      <parameter name="filename" value="I:\traces\SSASQueriesTrace.xel" />
      <parameter name="max_file_size" value="4096" />
      <parameter name="max_rollover_files" value="10" />
      <parameter name="increment" value="1024" />
      </target>
     </event_session>
    </XEvent>
    </Trace>
  </ObjectDefinition>
  </Create>

• jmetape

  Right there with Babe

  Points: 734

  More actions

  October 3, 2018 at 2:15 pm

  #2007956

  Update on this--it is an intermittent issue. Sometimes a trace started using the service account captures all the data, sometimes not.