Serilog 创建日志文件但不写入其中

Serilog creates the log file but doesn't write into it

所以我开始将 Serilog 与我的 ASP .NET Core 3.1 Web API 一起使用,如下所示:

public static void Main(string[] args)
{
    CreateHostBuilder(args).Build().Run();
}

public static IHostBuilder CreateHostBuilder(string[] args) =>                
    Host.CreateDefaultBuilder(args).ConfigureWebHostDefaults(webBuilder =>
    {
        webBuilder.UseStartup<Startup>()
                  .UseSerilog((hostingContext, loggerConfiguration) =>
       loggerConfiguration.ReadFrom.Configuration(hostingContext.Configuration));
     });   

但是,创建了日志文件但没有任何内容写入其中,无论我在哪里调用 [=12] =].我尝试使用不同的路径来避免某种类型的任何写入凭证问题,但无济于事。此外,尽管也设置了控制台日志,但我在 Visual Studio 的输出 window 中看不到任何内容。这是我在 appSettings.json 中写的内容:

"Serilog": {
"MinimumLevel": {
  "Default": "Debug"
},
"WriteTo": [      
  {
    "Name": "Console"
  },
  {
    "Name": "File",
    "Args": {
      "path": "log.txt",
      "rollingInterval": "Day",
      "retainedFileCountLimit": 7,
      "buffered": true
    }
  }
]
  },

我是不是漏掉了什么?

更新: OP edited the question after my answer 下面并删除了我指出的代码部分。


在你上面的例子中,你在你的应用程序的一开始就写到 Serilog,甚至在配置 Serilog 之前,所以你的消息只是被丢弃了...

为了做你想做的事,你需要先设置Serilog。

按照 Serilog.AspNetCore 存储库中的 EarlyInitializationSample 查看它是如何完成的,它看起来像这样:

using System;
using System.IO;
using Microsoft.AspNetCore.Hosting;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.Hosting;
using Serilog;

namespace EarlyInitializationSample
{
    public class Program
    {
        public static IConfiguration Configuration { get; } = new ConfigurationBuilder()
            .SetBasePath(Directory.GetCurrentDirectory())
            .AddJsonFile("appsettings.json", optional: false, reloadOnChange: true)
            .AddJsonFile($"appsettings.{Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT") ?? "Production"}.json", optional: true)
            .AddEnvironmentVariables()
            .Build();

        public static int Main(string[] args)
        {
            Log.Logger = new LoggerConfiguration()
                .ReadFrom.Configuration(Configuration)
                .Enrich.FromLogContext()
                .WriteTo.Debug()
                .WriteTo.Console(
                    outputTemplate: "[{Timestamp:HH:mm:ss} {Level:u3}] {Message:lj} {Properties:j}{NewLine}{Exception}")
                .CreateLogger();

            try
            {
                Log.Information("Getting the motors running...");

                CreateHostBuilder(args).Build().Run();

                return 0;
            }
            catch (Exception ex)
            {
                Log.Fatal(ex, "Host terminated unexpectedly");
                return 1;
            }
            finally
            {
                Log.CloseAndFlush();
            }
        }

        public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)
                .ConfigureWebHostDefaults(webBuilder =>
                {
                    webBuilder.UseStartup<Startup>();
                })
                .UseSerilog();
    }
}

Debugging and Diagnostics

When Serilog is not behaving as you expect, this may be caused by an internal exception or configuration issue. Here are a couple of ways to sort things out.