Tracking Events into Event Tracing in Windows

This topic applies to Windows Workflow Foundation 4 (WF4).

This sample demonstrates how to enable Windows Workflow Foundation (WF) tracking on a workflow service and emit the tracking events in Event Tracing for Windows (ETW). To emit workflow tracking records into ETW, the sample uses the ETW tracking participant (EtwTrackingParticipant).

The workflow in the sample receives a request, assigns the reciprocal of the input data to the input variable and returns the reciprocal back to the client. When the input data is 0, a divide by zero exception occurs that is unhandled that causes the workflow to abort. With tracking enabled, the error track record is emitted to ETW, which can help troubleshoot the error later. The ETW tracking participant is configured with a tracking profile to subscribe to tracking records. The tracking profile is defined in the Web.config file and provided as a configuration parameter to the ETW tracking participant. The ETW tracking participant is configured in the Web.config file of the workflow service and is applied to the service as a service behavior. In this sample, you view the tracking events in the event log using Event Viewer.

Workflow Tracking Details

Windows Workflow Foundation provides a tracking infrastructure to track the execution of a workflow instance. The tracking runtime creates a workflow instance to emit events related to the workflow lifecycle, events from workflow activities and custom events. The following table details the primary components of the tracking infrastructure.

The following table details the tracking records that the workflow runtime emits.

The tracking participant subscribes for a subset of the emitted tracking records using tracking profiles. A tracking profile contains tracking queries that allow subscribing for a particular tracking record type. Tracking profiles can be specified in code or in configuration.

To use this sample

1. Using Visual Studio 2010, open the EtwTrackingParticipantSample.sln solution file.

2. To build the solution, press CTRL+SHIFT+B.

3. To run the solution, press F5.

   By default, the service is listening on port 53797 (https://localhost:53797/SampleWorkflowService.xamlx).

4. Using Windows Explorer, open the WCF test client.

   The WCF test client (WcfTestClient.exe) is located in the <Visual Studio 2010 installation folder>\Common7\IDE\ folder.

   The default Visual Studio 2010 installation folder is C:\Program Files\Microsoft Visual Studio 10.0.

5. In WCF test client, select Add Service from the File menu.

   Add the endpoint address in the input box. The default is https://localhost:53797/SampleWorkflowService.xamlx.

6. Open the Event Viewer application.

   Before invoking the service, start Event Viewer from the Start menu, select Run and type in eventvwr.exe. Ensure that the event log is listening for tracking events emitted from the workflow service.

7. In the tree view of the Event Viewer, navigate to Event Viewer, Applications and Services Logs, and Microsoft. Right-click Microsoft and select View and then Show Analytic and Debug Logs to enable the analytic and debug logs

   Ensure that the Show Analytic and Debug Logs option is checked.

8. In the tree view in Event Viewer, navigate to Event Viewer, Applications and Services Logs, Microsoft, Windows, Application Server-Applications. Right-click Analytic and select Enable Log to enable the Analytic log.

9. Test the service using the WCF test client by double-clicking GetData.

   This opens the GetData method. The request accepts one parameter and ensures that the value is 0, which is the default.

   Click Invoke.

10. Observe the events emitted from the workflow.

    Switch back to Event Viewer and navigate to Event Viewer, Applications and Services Logs, Microsoft, Windows, Application Server-Applications. Right-click Analytic and select Refresh.

    The workflow events are displayed in the event viewer. Notice that workflow execution events are displayed and that one of them is an unhandled exception that corresponds to the error in workflow. Also, a warning event is emitted from the workflow activity, which indicates that the activity is throwing a fault.

11. Repeat steps 9 and 10 with an input of data other than 0, so that no error is thrown.

Tracking profiles allow you to subscribe to events that are emitted by the runtime when the state of a workflow instance changes. Depending on your monitoring requirements, you can create a profile that is very coarse, which subscribes to a small set of high-level state changes on a workflow. On the other hand, you can create a very precise profile whose output is rich enough to reconstruct the execution later. The sample demonstrates the events emitted from the workflow runtime to ETW using the HealthMonitoring Tracking Profile, which emits a small set of events. A different profile that emits more workflow tracking events is also provided in the Web.config that is named Troubleshooting Tracking Profile. When the .NET Framework 4 is installed, a default profile with an empty name is configured in the Machine.config file. This profile is used by the ETW tracking behavior configuration when no profile name or an empty profile name is specified.

The health monitoring tracking profile emits workflow instance records and activity fault propagation records. This profile is created by adding the following tracking profile to a Web.config configuration file.

<<tracking>
      <profiles>
        <trackingProfile name="HealthMonitoring Tracking Profile">
          <workflow activityDefinitionId="*">
            <workflowInstanceQueries>
              <workflowInstanceQuery>
                <states>
                  <state name="Started"/>
                  <state name="Completed"/>
                  <state name="Aborted"/>
                  <state name="UnhandledException"/>
                </states>
            </workflowInstanceQuery>
           </workflowInstanceQueries>
            <faultPropagationQueries>
              <faultPropagationQuery faultSourceActivityName ="*" faultHandlerActivityName="*"/>
            </faultPropagationQueries>
          </workflow>
        </trackingProfile>
       </profiles>
</tracking>

The profile can be changed by changing the EtwTrackingParticipant configuration to the following.

<behaviors>
      <serviceBehaviors>
        <behavior>
          <etwTracking profileName="HealthMonitoring Tracking Profile"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>

To clean up (Optional)

1. Open Event Viewer.

2. Navigate to Event Viewer, Applications and Services Logs, Microsoft, Windows, Application Server-Applications. Right-click Analytic and select Disable Log.

3. Navigate to Event Viewer, Applications and Services Logs, Microsoft, Windows, Application Server-Applications. Right-click Analytic and select Clear Log.

4. Choose the Clear option to clear the events.

Known Issue

Note:

There is a known issue in the Event Viewer where it may fail to decode ETW events. You may see an error message that looks like the following. The description for Event ID <id> from source Microsoft-Windows-Application Server-Applications cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If you encounter this error, click refresh in the actions pane. The event should now decode properly.

Note:

The samples may already be installed on your computer. Check for the following (default) directory before continuing. <InstallDrive>:\WF_WCF_Samples If this directory does not exist, go to Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF) Samples for .NET Framework 4 to download all Windows Communication Foundation (WCF) and WF samples. This sample is located in the following directory. <InstallDrive>:\WF_WCF_Samples\WF\Basic\Tracking\EtwTracking

See Also

Other Resources

AppFabric Monitoring Samples