Unable to set providers using EventPipeConfig

[tmds]

Probably this is not a bug, but me doing it wrong.

I'm using .NET 6.0.107.

I have an app:

var client = new HttpClient();

var response = await client.GetAsync("https://nuget.org");

Console.WriteLine(response.StatusCode);

I'd like to see a trace that includes the HTTP events.

I've set these variables:

DOTNET_EventPipeConfig=*
COMPlus_EventPipeOutputPath=/tmp/trace
COMPlus_EventPipeConfig=*
COMPlus_EnableEventPipe=1

I execute the app:

bin/Debug/net6.0/console

I now have a file at /tmp/trace.

I read it (on another shell that doesn't have the envvars set) using:

using System;
using Microsoft.Diagnostics.Tracing;
using Microsoft.Diagnostics.Tracing.Etlx;
using Microsoft.Diagnostics.Tracing.Parsers;

namespace console
{
    class Program
    {

        static void Main(string[] args)
        {
            if (args.Length < 1)
            {
                Console.WriteLine("You must specify a nettrace file.");
                return;
            }

            using (var traceLog = new TraceLog(TraceLog.CreateFromEventPipeDataFile(args[0])))
            {
                var traceSource = traceLog.Events.GetSource();

                traceSource.AllEvents += delegate (TraceEvent data) {
                    Console.WriteLine("{0}", data);
                };

                traceSource.Process();

           }
        }
    }
}

The output doesn't have any HTTP events.

cc @noahfalk @dotnet/area-system-diagnostics-tracing @adamsitnik

[noahfalk]

@davmason

At first glance I would guess the issue is that "*" isn't a valid setting for DOTNET_EventPipeConfig. https://docs.microsoft.com/en-us/dotnet/core/diagnostics/eventpipe#trace-using-environment-variables
https://docs.microsoft.com/en-us/dotnet/core/diagnostics/well-known-event-providers

Perhaps you want DOTNET_EventPipeConfig=System.Net.Http?

[tmds]

At first glance I would guess the issue is that "*" isn't a valid setting for DOTNET_EventPipeConfig.

I think this has worked for me in the past.

Perhaps you want DOTNET_EventPipeConfig=System.Net.Http?

With

COMPlus_EventPipeOutputPath=/tmp/trace
COMPlus_EventPipeConfig=System.Net.Http
COMPlus_EnableEventPipe=1

I still don't get any HTTP related events.

[noahfalk]

Hopefully @davmason can take a look.

[davmason]

@tmds, the configuration Noah gave should have worked - do you get any events at all in the trace file? You could also try COMPlus_EventPipeConfig=System.Net.Http:0:5 and see if that works

[tmds]

@tmds, the configuration Noah gave should have worked - do you get any events at all in the trace file?

Yes, there are events, most of them are Loader/... events.

You could also try COMPlus_EventPipeConfig=System.Net.Http:0:5 and see if that works

That doesn't work either.

[davmason]

If you are seeing loader events that makes me suspicious. If you have COMPlus_EventPipeConfig=System.Net.Http then you should only be receiving those events and we shouldn't enable the default providers.

For a sanity check do you have DOTNET_EventPipeConfig still set? It may be picking that up and ignoring the COMPlus one

[tmds]

For a sanity check do you have DOTNET_EventPipeConfig still set? It may be picking that up and ignoring the COMPl

I only had the 3 envvars set mentioned in the comment.

If you are seeing loader events that makes me suspicious. If you have COMPlus_EventPipeConfig=System.Net.Http then you should only be receiving those events and we shouldn't enable the default providers.

I get the loader events with COMPlus_EventPipeConfig=System.Net.Http set.

[wfurt]

I think the problem may be the name. Try to use Private.InternalDiagnostics.System.Net.Http @tmds. (if I remember correctly the name changed in 6.0 e.g. for 5.0 the old name would still work)

[tmds]

I think the problem may be the name.

The name is ok. I can see events for it using EventListener.

Based on what was said, it looks like the EventPipeConfig isn't getting picked up at all.

[tmds]

@davmason can you please take a look?

[davmason]

Yes, I will take a look soon. I am running in to a different issue preventing me from debugging your issue