in ASP.NET core (.NET5) how can i write logs for each request on separate files? Using Serilog or other

Question

I'm new to .NET and to webservice development, so i'm not exactly sure how to implement the requirement i have.

• My webservice gets a POST request with some data, which i need to process to generate a pdf file: name_YYYYMMDDHHmmss.pdf.
• For monitoring this i want to have a separate logfile for each request, named like the output file: name_YYYYMMDDHHmmss.log
• I would like to avoid passing a config object into every class/function in which i need to add stuff to the log file

I've managed to install Serilog and it works for what i need, but not when i get concurrent requests. I'm also not exactly sure how simultaneous requests are handled in .NET (i have no thread specific code written so far), but as far as i can tell, when i change Global Logger file name, that object is shared across all threads so all of them write to the same file.

I've looked at a bunch of solutions, but i haven't managed to find nothing that suits this, and it seems most people have everything into 1 file...

Is there any clue or tips you can give me? I'm open to using something other than Serilog.

Answer 1

One way to have dynamic file names based on a specific context is by using the Serilog.Sinks.Map and then, via a middleware in the request pipeline, you can add a property to the log context that drives the file name to be used when writing to the log.

Examples of similar usage of Serilog.Sinks.Map to decide which file name to use at run-time:

• Serilog - can not log to multiple files based on property
• In Serilog dynamically changing log file path?

Answer 2

The best solution that I found to this problem was using Serilog.Sinks.Map. I configured my Logger something like this:

Log.Logger = new LoggerConfiguration()
    .WriteTo.Map("Name", "Default", (name, wt) => {
        var fileName = name == "Default" ? "log" : $"{log-{name}}" 

        wt.File($"./{fileName}-.txt");
    }).CreateLogger();

Then on my controller, on each method where I needed this feature, I enclosed all the instructions inside a LongContext like this:

[HttpGet]
public IHttpActionResult Get() {
   using (LogContext.PushProperty("Name", "theFileName") {
       // ...
       _myService.Method1();
       // ...
   }
}

public class MyService : IMyService {
   // ...

   public void Method1() {
      // ...
      Log.Information("This is what happened at this point…");
      // ...
   }
   // ...
}

So all the Log's inside will use that context and it will write on a different file with the name you set for that context without having to modify any Log.Information/Error/Warning/etc that you already have on your code. This is the ugly part... you have to define a context on a root place in order to make those Logs write on a different file. So for a controller method, the first thing you have to do is to enclose all with a LogContext.