Note: This document is a work in progress and is captured for the benefit of knowledge transfer.
WebRTC traces are included in the UWP library and are equivalent to what is present in Chrome. Currently they are not wired to the managed API surface. The notes below refer to enabling traces in native code. This will be enabled for managed clients in a future release.
Google's sample to enable traces can be found here. It is an Android component where the traces are saved to the file.
Call rtc::tracing::SetupInternalTracer() and after that rtc::tracing::StartInternalCapture() with a file name as a parameter. After tracing session is ended, you can visualize the results in Chrome browser using chrome://tracing application.
After tracing session is ended, the results can be viewed in Chrome (chrome://tracing application) and I believe any of the graphical tools that were mentioned in first section of this document should be able to show the out put.
Regarding this section, I found this explanation useful as well: https://github.com/webrtc-uwp/webrtc-uwp-sdk/issues/80#issuecomment-434828016