HttpLoggingMiddleware log connection properties

[Tratcher]

HttpLoggingMiddleware will log headers, properties (method, path, query, etc.), and body. However it will not log any information about the connection (Remote IP, local IP, ports, client certificate, TLS version, etc.).

Here's an example from our docs where the remote IP is relevant in the request logs:
https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-5.0#troubleshoot

Which fields should we make available to log, and what granularity should we provide in the enum to enable them?

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.

[BrennanConroy]

Triage: This will be possible with some upcoming work, question is do we want this to be a first-class feature
Backlogging to see if there are customer asks for it.

[Kahbazi]

+1 on logging remote IP in HttpLoggingMiddleware.

Also could there be a shared feature between this middleware and Forwarded header middleware so we could have both remote IP and the end-user client IP?

[Tratcher]

+1 on logging remote IP in HttpLoggingMiddleware.

Also could there be a shared feature between this middleware and Forwarded header middleware so we could have both remote IP and the end-user client IP?

Depending on the ordering, one of those values will be available in the headers.

I do still want to re-do the forwarded headers middleware to store the original values in a feature, but that's out of scope here for now.