Remove IKestrelTrace

[JamesNK]

IKestralTrace was added before it was easily possible to unit test logs.

See #31562 (comment)

We should remove the interface and change KestrelTrace into a static class. Will save making interface method calls.

Will likely require a lot of changes to unit tests.

Repeat for ISocketTrace and IQuicTrace.

[JamesNK]

@davidfowl @halter73

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[davidfowl]

@gfoidl want to take a stab at this?

[gfoidl]

I'll give it a try 😃

[gfoidl]

Once #31596 is merged, I'm starting, otherwise there'll be a merge conflict.

[fvoronin]

@gfoidl, JFYI, #31596 was merged

[gfoidl]

Thanks for the info!
Will start soon working on it -- and will look into #32087 as well.

[gfoidl]

Update: I'd like to wait on dotnet/runtime#51927. This unblocks the usage here for source generators.

[adityamandaleeka]

@gfoidl Are you still interested in taking on this issue?

[JamesNK]

Also, Kestrel and transport logs have been updated to use source generators.

#34910

[gfoidl]

Yes, my interest is still there, but I'm a bit sick at the moment (and my brain not working at the level I'd like it to work). So I won't start before next week.

[adityamandaleeka]

@gfoidl Sorry to hear that you're not feeling well, and hope you get better soon. Please don't feel rushed to work on this until you are fully recovered.

I'm going to change the milestone for now just for tracking purposes. We can add a milestone again once we know when it'll land.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.