serilog-aspnetcore | Serilog integration for ASP.NET Core

You can use UseSerilogRequestLogging like below to add custom properties like Username and IPAddress. You should add it after UseAuthentication to get logged in Username.

One workaround I found is manually logging the error from my global exception middleware. In Program.cs, remove the following line:

The first rule of Serilog troubleshooting is to enable SelfLog and see what error messages are being thrown by the Serilog sink.

Most likely it's a permission issue (i.e. the account doesn't have permission to write to the folder you're attempting to write to).

.WriteTo.File("logs.txt", ...) writes to the current working directory, and in the case of Windows Services usually means %WINDIR%\System32 - which I'm sure it's not the place you want to store your logs anyway.

Thus you need to be more explicit about the path you want to write your logs to, and make sure it points to a folder the account used for running the service will have write access to.

A common pattern is to define the path in a configuration file (e.g. appSettings.json) and retrieve that.

If you're looking to write to the same folder where your Windows Service binaries are, a reliable way nowadays is to use Process.GetCurrentProcess().MainModule?.FileName (1). E.g: