This repository was archived by the owner on Dec 13, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 13, 2018. It is now read-only.
Integrated logs for aspnet and wilson #331
Description
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.
Activity
leastprivilege commentedon Jul 2, 2015
Oh really - why is that? Must be an artifact from the Katana version.
kevinchalet commentedon Jul 2, 2015
@leastprivilege
ILoggeris part of the new logging block and has nothing to do with Katana: https://github.com/aspnet/Logging 😄leastprivilege commentedon Jul 2, 2015
Oh really? ;) So who is using EventSource then - and why?
kevinchalet commentedon Jul 2, 2015
EventSourceis used by Wilson for its internal logging.Why? I dunno: #258 (comment)
brentschmaltz commentedon Jul 3, 2015
Because ILogger is not available for some of the customers of Wilson.
kevinchalet commentedon Jul 3, 2015
Then it might be a good idea to list those targets and add them to aspnet/Logger.
/cc @Eilon
tushargupta51 commentedon Jul 6, 2015
Aligning the logging experience of Wilson with ADAL is one reason. ADAL uses EventSource.
Eilon commentedon Sep 3, 2015
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.