seq-logging-aspnetcore VS NLog

I have a minimal example for logging with Serilog if you're interested: https://github.com/hyrmn/seq-logging-aspnetcore

If this helps, here is an example wire up of Serilog and Seq with minimal api. https://github.com/hyrmn/seq-logging-aspnetcore/blob/main/Program.cs

What is it you're trying to accomplish? Either this is a regular expression problem (not really dotnet related) or you should try using structured logging, with a provider and sink that support it so you don't have to use regular expressions.

NLog

Log4Net does not get that much attention any more. From my understanding it served as an alternative for Log4J, but today better and more modern solutions have been created. I migrated a codebase over to .NET Core a couple of years ago, and it seemed that Log4net had issues running on Linux because of kernel calls inside their codebase. If you look at the version history on NuGet, it had just 3 patch releases last year. As an alternative, I would suggest to check out NLog.

C# -> Built in Logger, Log4Net, Serilog, NLog, e.t.c.

I would like to use a proper logger like https://github.com/nlog/nlog

I'm going to look at psframework mentioned elsewhere, but i make use of .NET NLog https://nlog-project.org/. it's not terribly hard to wire up, and is pretty feature rich.

have a look at this https://github.com/nlog/nlog/wiki/Context you dont want to make your own logger 99% of them time

For a more structured log file*) layout, you could use something like NLog with a PS wrapper.

NLog is another option here, with the buffering wrapper around an email target.