Closed eSamchuk closed 2 years ago
Hi @eSamchuk!
Sorry for the delay. Can you provide us a full sample program to reproduce your issue?
Thanks, Christian
Sorry for the late response.
Have you tried to create and register two different loggers (logging pipelines) in the ASP.NET Core dependency container and inject them as separate ILogger instances as needed.
Possibly you could also have only one logging pipeline but use sub-loggers as shown here: https://github.com/serilog/serilog/wiki/Configuration-Basics#sub-loggers
My goal is to split logs into different tables depending on log entry level, so that Information and Warning records are separated from Error and Fatal. There are some guides on this topic, I used several of them, but without any success.
What I know and what I've tried so far:
sa
login to connect to my logging database, so it is not about permissions, but with no success.CREATE TABLE
,SELECT
andINSERT
autoCreateSqlTable=true
and required tables were created, but no records were written to them.autoCreateSqlTable=true
and used recommended script to create required tables ahead of time.batchPostingLimit
has been set to 1 to enforce immediate log writing (Not sure that this could help at all, but gave it a try)What am I missing?