Explore whether to enable Unix Domain Socket support for Diagnostics Server on Windows

[josalem]

This will require changes in the IPC library in src/native/eventpipe as well as the diagnostics client. It will only work in versions of Windows newer than Win 10 1804 (TODO: verify this version). This may cause complications as we can't enable/disable this based on a RID, e.g., win7. We'll need some kind of runtime check to determine whether we should use a UDS.

CC @dotnet/dotnet-monitor @lateralusX @tommcdon

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This will require changes in the IPC library in src/native/eventpipe as well as the diagnostics client. It will only work in versions of Windows newer than Win 10 1804 (TODO: verify this version). This may cause complications as we can't enable/disable this based on a RID, e.g., win7. We'll need some kind of runtime check to determine whether we should use a UDS.

CC @dotnet/dotnet-monitor @lateralusX @tommcdon

Author:	josalem
Assignees:	-
Labels:	EventPipe, area-Diagnostics-coreclr
Milestone:	7.0.0

[AloisKraus]

Is this still on the roadmap? No dot-monitor support for Windows? ETW also does not work. What should one use to monitor not only CPU but also CPU Sampling on Windows Containers which are running in HyperV isolation?