[HttpClientFactory] ILoggerFactory dependency issue

[CodeBlanch]

Original post: #77312 (comment)

Description

I've run into (essentially) a circular reference issue because DefaultHttpClientFactory takes a depedency on ILoggerFactory via ctor injection.

OpenTelemetry has implemented an ILoggerProvider which may use HttpClient to export logs to different backends. We use IHttpClientFactory to allow users to control/customize the HttpClient instance. During construction of ILoggerFactory this provider is created which tries to access IHttpClientFactory which again tries to acces ILoggerFactory.

ILoggerFactory -> OpenTelemetryLoggerProvider -> LogExporter -> IHttpClientFactory -> ILoggerFactory

Ideally DefaultHttpClientFactory would not depend on ILoggerFactory so that it may be used in logging scenarios.

/cc @CarnaViire @noahfalk

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Original post: #77312 (comment)

Description

I've run into (essentially) a circular reference issue because DefaultHttpClientFactory takes a depedency on ILoggerFactory via ctor injection.

OpenTelemetry has implemented an ILoggerProvider which may use HttpClient to export logs to different backends. We use IHttpClientFactory to allow users to control/customize the HttpClient instance. During construction of ILoggerFactory this provider is created which tries to access IHttpClientFactory which again tries to acces ILoggerFactory.

ILoggerFactory -> OpenTelemetryLoggerProvider -> LogExporter -> IHttpClientFactory -> ILoggerFactory

Ideally DefaultHttpClientFactory would not depend on ILoggerFactory so that it may be used in logging scenarios.

/cc @CarnaViire @noahfalk

Author:	CodeBlanch
Assignees:	-
Labels:	area-Extensions-HttpClientFactory
Milestone:	-

[karelz]

Triage: Looks nasty without a workaround.
We should ask the providers to create HttpClient without public logging and we need to switch internal logging to EventSource instead of ILogger.