You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 24, 2021. It is now read-only.
Each iteration causes an IterationStart and IterationStop message to be emitted. On .NET 4.6 (and hopefully CoreCLR, though I will check) this means an Activity will be allocated for the Iteration (as per http://blogs.msdn.com/b/vancem/archive/2015/09/14/exploring-eventsource-activity-correlation-and-causation-features.aspx). All ETW events that take place between the start and stop messages will get this activity ID and thus can be correlated back to the original iteration. We should set up collectors to support this.
The text was updated successfully, but these errors were encountered:
Each iteration causes an
IterationStart
andIterationStop
message to be emitted. On .NET 4.6 (and hopefully CoreCLR, though I will check) this means an Activity will be allocated for the Iteration (as per http://blogs.msdn.com/b/vancem/archive/2015/09/14/exploring-eventsource-activity-correlation-and-causation-features.aspx). All ETW events that take place between the start and stop messages will get this activity ID and thus can be correlated back to the original iteration. We should set up collectors to support this.The text was updated successfully, but these errors were encountered: