NLog for .Net Core is not logging Debug information

Viewed 1010

I've recently started writing .Net Core applications and I'm using NLog for my logging. I came up with the following NLog.config file. This will log if I use _log.LogInformation("Log an INFO"); but not if I use _log.LogDebug("Log a DEBUG");.

I do not have any logging settings in my appsettings.json file. I typically write console applications and VisualStudio template for console apps does not have any logging automatically added to appsettings.

I'm using .Net Core 3.1 with the following NLog package.

<PackageReference Include="NLog.Web.AspNetCore" Version="4.9.3" />

Anyone see why using the Debug wouldn't write to the log file?

<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      autoReload="true">

  <!-- enable asp.net core layout renderers -->
  <extensions>
    <add assembly="NLog.Web.AspNetCore"/>
  </extensions>

  <variable name="LogDirectory" value="D:\logs\ProjectName"/>

  <!-- the targets to write to -->
  <targets>
    
    <target xsi:type="File" 
      name="DefaultTarget" 
      fileName="${LogDirectory}\LogFile.log"
      layout="${longdate} | ${callsite} | ${message}"
      archiveAboveSize="3145728"  
      archiveEvery="Day"
      archiveFileName = "${LogDirectory}/Archive/{#}.log"  
      archiveNumbering = "DateAndSequence"            
      archiveDateFormat = "yyyyMMdd"  
      maxArchiveFiles = "21"            
    />

    <target name="ConsoleTarget"
      xsi:type="Console"
      layout="${longdate} ${logger:shortName=True} ${message} ${onexception:EXCEPTION OCCURRED\:${exception:format=type,message,StackTrace,method:maxInnerExceptionLevel=8:innerFormat=type,message,StackTrace,method}}"
    />
    
  </targets>  
  <rules>
    <logger name="Microsoft.*" maxlevel="Info" final="true" /> <!-- BlackHole without writeTo -->
    <logger name="*" minlevel="Debug" writeTo="DefaultTarget,ConsoleTarget" />
  </rules>
</nlog>
0 Answers
Related