Brian Robbins

Yes - for .NET Core, there is an eventsource: https://github.com/dotnet/runtime/blob/13733cdd969842de9c36235d730a604ce55ee729/src/libraries/System.Net.Sockets/src/System/Net/Sockets/NetEventSource.Sockets.cs#L10.

This seems reasonable. Where specifically would you want to see this? Would you be looking to have this information in the events view?

@EmosewaMC, I recommend that you look at https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace. It is possible to convert from `nettrace` to `speedscope` via `dotnet-trace convert`. You can also specify the output format directly if using...

Oh, I see. Sorry, I mis-read your question. I am not aware of a way to do this via the command line. It is available through the `Save View As`...

LTTng output is controlled by environment variable. Can you confirm that you set `COMPlus_EnableEventLog=1` for the `dotnet` process?

Environment variables that start with `DOTNET_` are treated the same as those that start with `COMPlus_`. `COMPlus_` is the original/historical prefix. Given that the trace is that large, I suspect...

The log shows that all of the LTTng commands failed, because a channel couldn't be created. Can you please try running the following: ``` lttng create lttng add-context --userspace --type...

Given that these commands don't work outside of `perfcollect`, it doesn't sound like a bug in `perfcollect`. Since this is inside a container, is it possible for you to try...

It does sound like that. You may need to attach a debugger to the failing LTTng command to get more details.

@ilabutin, the WPF version will remain and is worth investing in. We would like to have a JS-based solution at some point, but it's not clear when that will happen.