Remove filters for ILoggers created by customer DI

[brettsam]

We need to be less restrictive on filtering logging categories. Today if someone creates a logger that is not in one of our "accepted" lists, we'll filter it away. You can get around this by adding one or more filters to get those categories flowing again, but this shouldn't be necessary.

The below settings will allow any category that starts with "OrderService" to be logged at "Information" and above levels.

{
  "version": "2.0",
  "logging": {
    "logLevel": {
      "OrderService": "Information"
    }
  }
}

[sandeepiiit]

@brettsam Thanks for the host.json workaround. Is there a way to specify log levels differently for development vs production environments?

[bchrisb]

@brettsam when you say: The below settings will allow any category that starts with "OrderService" to be logged at "Information" and above levels. what is a "category"? I am experiencing this bug but I'm not quite sure what the workaround is? See my code below:

private ILogger<ServiceLogger> _logger;
private readonly string _version;
private readonly string _deploymentRegion;

public ServiceLogger(ILogger<ServiceLogger> logger, IAppSettings appSettings)
{
	_logger = logger;
	_version = appSettings.Version;
	_deploymentRegion = appSettings.DeploymentRegion;
}

And then my host.json:

{
  "version": "2.0",
  "logging": {
	"logLevel": {
	  "ServiceLogger": "Information"
	}
  }
}

I still don't get any logs. What am I missing?

[bchrisb]

@brettsam sorry, I've just found the answer to my own question by looking at this: #4425 (comment)