Multiple Serilog Loggers

Question

Is it possible to have multiple serilog loggers? Currently within my WebApi I can call Log.Information for example to log an information event, but is there a way that I can instead make different logs and call ExternalLog.Information or AuthenticationLog.Information from my controller? The purpose behind this is that my web api is currently working with multiple different databases for different yet interrelated projects, and I would like to store logs within each of these databases that pertain to them instead of needing to create an additional logging database if at all possible.

A better solution, that I figure is less likely is, can I map individual controllers to a log, so that any time that a specific controller calls log, it writes to the AuthenticationLog for example.

Sure, you can make multiple loggers. What's stopping you from grabbing the ILogger that new LoggerConfiguration().CreateLogger(); makes? — mason
@mason - "Sure, you can make multiple loggers. What's stopping you from grabbing the ILogger that new LoggerConfiguration().CreateLogger(); makes? " Worked for me. Seems a lot simpler than sublogging. It seems to me that sublogging is to break a single source of log events into logs for that particular part of the app? — Eric Snyder

dmoore1181 dmoore1181 · Accepted Answer · 2019-03-27T20:42:57

I believe that the answer to this question is to use subloggers, rather than separate loggers. I have found that you can do .WriteTo.Logger and filter further in there. I will accept this as the answer if nobody else has a better solution (and of course if I am able to get it to work). I need to be able to filter on the controller or action name, which at this time I have a second stack overflow question out to figure out how to get that data. Serilog with Asp.net Web Api not using enricher

Multiple Serilog Loggers

1 Answers