Configurable logging

[RoadTrain]

Hello! Thanks for the great library.

I've been using it in my application for a while via nuget package ReportGenerator.Core, and now I wonder how to set up logging in a way that internal library logs are not printed to console, but instead redirected to the application-level logger (I'm using Serilog).

Is there a way to configure that? From what I see from source code, class loggers are resolved once, and are stored in static fields, which will prevent runtime reconfiguration.

Am I missing something?

[danielpalme]

That's correct. The logger is currently not configurable.

[RoadTrain]

@danielpalme Would you welcome contributions to make it configurable? Maybe you already have a vision of how it should be done?

[danielpalme]

Sorry, my initial reply was wrong or at least not complete.

You can implement a custom Logger and custom LoggerFactory.

Then you can register your custom factory:

LoggerFactory.Configure(new MyCustomLoggerFactory());

That way you should be able to write a custom adapter to your logging system.

[RoadTrain]

Thanks, I'll give it a try.
What do you think of extending this class with another method like:

LoggerFactory.Configure(Action<VerbosityLevel, string> logDelegate);

So that consumers would need to only provide a logger delegate instead of implementing their own ILogger and ILoggerFactory?

If you're not against such an approach, I can draft a pull request.

[danielpalme]

Sure, that should be no problem.

[danielpalme]

I created a draft here: #446
What do you think?