Integrated logs for aspnet and wilson

[tushargupta51]

Microsoft.Aspnet.Authentication.OpenIdConnect uses ILogger to log events whereas Wilson uses EventSource based logging. Currently, there is no easy way for a user using OIDC to get an integrated log from both aspnet and wilson (OIDC takes a hard dependency on Wilson). They have to configure both the loggers separately and it is very difficult to debug using the separated logs.

[leastprivilege]

Oh really - why is that? Must be an artifact from the Katana version.

[kevinchalet]

@leastprivilege ILogger is part of the new logging block and has nothing to do with Katana: https://github.com/aspnet/Logging 😄

[leastprivilege]

Oh really? ;) So who is using EventSource then - and why?

[kevinchalet]

EventSource is used by Wilson for its internal logging.

Why? I dunno: #258 (comment)

[brentschmaltz]

Because ILogger is not available for some of the customers of Wilson.

[kevinchalet]

Then it might be a good idea to list those targets and add them to aspnet/Logger.

/cc @Eilon

[tushargupta51]

Aligning the logging experience of Wilson with ADAL is one reason. ADAL uses EventSource.

[Eilon]

Both ASP.NET 5 components and Wilson can (or will be able to) write to EventSource, and that is the best way to get unified logs.