Skip to content
This repository has been archived by the owner on Feb 24, 2021. It is now read-only.

Add minimal ETW tracing to Kestrel for request correlation #21

Open
analogrelay opened this issue Sep 15, 2015 · 0 comments
Open

Add minimal ETW tracing to Kestrel for request correlation #21

analogrelay opened this issue Sep 15, 2015 · 0 comments

Comments

@analogrelay
Copy link
Contributor

We should add RequestStart and RequestStop ETW events to Kestrel so we can easily correlate Stress-related events within a single request. This will also be useful for performance monitoring of Kestrel and user web apps. We don't need detailed ETW, just a start/stop tracker. ETW handles the rest so that other ETW events get tagged with the right Activity ID

Tracking this here for now just to discuss this before we go to far. I'll make an issue in the Kestrel repo when we actually have a plan. Obviously whatever we do has to be cross-platform so it'll likely have to be ifdef/PlatformHelper gated for now.

/cc @davidfowl @DamianEdwards @halter73

@analogrelay analogrelay self-assigned this Sep 15, 2015
@analogrelay analogrelay removed their assignment Nov 19, 2015
@davidfowl davidfowl reopened this Feb 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants