Configuration and Filtering changes

[BrennanConroy]

• Add void AddProvider(string providerName, ILoggerProvider provider) to LoggerFactory
• LoggerFactory(IConfiguration config) will be the way to add configuration to our factory
• Support named providers
  • Check typeof(type).FullName
  • Name passed into AddProvider wins always
• Example format:

{
  "Logging": { // default values unless otherwise specified
    "LogLevel": {
        "System": "Trace"
    },
    "Console": {
        "LogLevel": {
          "Microsoft.Extensions": "Warning"
        }
    },
    "CustomProvider": { // e.g. factory.AddProvider("CustomProvider", new MyCustomProvider())
      "LogLevel": {
        "System": "Information"
      }
    }
  }
}

- [ ] Remove ability to call AddProvider whenever you want, only allowed during startup

• Obsolete AddConsole(this ILoggerFactory factory, IConfiguration configuration)

Figure this out:

• Obsolete void AddProvider(ILoggerProvider provider) on ILoggerFactory

Stretch goal:

• Add AddFilter(string providerName, Func<string, LogLevel, bool> filter) to LoggerFactory
  • AddFilter is additive

[cwe1ss]

Will you react to changes in the underlying configuration system?

My desired scenario: Configuration is loaded from an external system like Consul. I want to be able to change the logging configuration in-flight without having to restart the application.

[BrennanConroy]

Yeah, we will handle config changes at runtime.