Monitoring Architecture

Here’s how AppFabric monitoring works. Event data is emitted from WCF and WF services and is sent to a high-performance Event Tracing for Windows (ETW) session. The data sent to an ETW session includes WCF analytic trace events and WF tracking record events emitted by using the ETW Tracking Participant. An Event Collector instance collects this event data from an ETW session and stores the data in the Monitoring database. AppFabric monitoring tools can read these events when they are persisted in the database.

These steps map to their corresponding numbers in the following diagram. They describe how analytic tracing events and tracking records are sent to an ETW session, and then forwarded by the Event Collector service to an AppFabric Monitoring database. AppFabric tools read the data from the monitoring database to compute dashboard metrics and display instrumentation events.

  1. Analytic tracing events are emitted from a WCF service to ETW.

  2. Tracking record events are emitted by the ETW Tracking Participant to ETW.

  3. An instance of the Event Collector service collects the events from an ETW session and sends them to a Monitoring database.

  4. The Monitoring database stores the event data that was emitted from WCF and WF services.

  5. The AppFabric monitoring tools present in their user interface the events in the Monitoring database.

ETW Tracking and Tracing Monitoring Architecture

See Also


Event Collection Service
Monitoring Store

Other Resources

Tracking Participants
Analytic Tracing with ETW