![]() ![]() I’ve updated the module above so that it no longer supports dependency injection of ILogger and ILogger instances are still created with the declaring type but also in a format that would allow Azure Functions to write the log entries. This also does not match the expected filter and log messages are also filtered out. ![]() Additionally, the LoggerModule originally posted above also didn’t work for ILogger because it used factory.CreateLogger(declaringType) which creates the logger name from declaringType.FullName. ![]() What this means is that currently (since the code from 19th December 2017 was released) Azure Functions will not work when using ILogger. This does not conform to either of the values that Azure Functions likes so the log messages are filtered out. The way ILogger is created by LogFactory uses the name derived from typeof(T).FullName. Any logger that does not have its name matching this format will have its log messages filtered out. ![]() The filter looks at whether the logger name is either Function.Something or. Public static class ContainerConfig Īzure Functions (v2 beta) applies a filter out of the box for ILogger. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |