NLog在Azure中不起作用

Question

I'm trying to use NLog with an Azure Web App. Everything works on my local PC, but when I deploy to Azure it doesn't work at all. I've tried with different targets like file and Azure table storage. Both work perfectly on my PC but not in Azure. I'm using asp.net core.

Here is my NLog config for the table storage.
this configuration works when I execute the program from my local PC. I can see the entries in the Azure table storage.

<?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"
  >

  <extensions>
    <add assembly="NLog.Extensions.AzureTableStorage"/>
  </extensions>
  <targets>

    <target xsi:type="AzureTableStorage" name="allfile" 
            PartitionKey="nlog-all-${date}.${logger}"
            RowKey="${ticks}.${guid}"
            ConnectionString="**REMOVED**"
            tableName="**REMOVED**"
                 layout="${longdate}|${logger}|${uppercase:${level}}|${message} ${exception}" />

    <target xsi:type="AzureTableStorage" name="ownFile"
            PartitionKey="nlog-own-${date}.${logger}"
            RowKey="${ticks}.${guid}"
            ConnectionString="**REMOVED**"
            tableName="**REMOVED**"
              layout="${longdate}|${logger}|${uppercase:${level}}|${message} ${exception}" />
    <target xsi:type="Null" name="blackhole" />
  </targets>

  <rules>

    <!--All logs, including from Microsoft-->
    <logger name="*" minlevel="Trace" writeTo="allfile" />

    <!--Skip Microsoft logs and so log only own logs-->
    <logger name="Microsoft.*" minlevel="Trace" writeTo="blackhole" final="true" />
    <logger name="*" minlevel="Trace" writeTo="ownFile" />
  </rules>
</nlog>

Answer 1

I noticed that the configuration file NLog.config was not getting updated (or is being overwritten) in Azure. Renaming the configuration file to something different solved my problem. However, I consider this a workaround only.

The NLog.config in Azure seems to be the one coming as example, and contains no targets at all.

Answer 2

It looks like there are some transformation issues & nothing to do with Azure website.

I would suggest following ways to fix it more permanently:

1. Easy Way : Cleate nlog.build.config for each environment & set "Copy to Output Directory" to Always. Please do not add any transformation in the this configs. In web.build.config, you just add transform different nlog files.
2. Alternative to Easy Way : You can always copy your code from nlog.config into web.config & provide transformation in web.build.config files.
3. Hard Way: You can use tools like slow cheetah to do actual transformation. https://www.c-sharpcorner.com/article/transform-config-using-slow-cheetah/ .