CODEWITHSUNDEEP
asp.net-corelogging
djack109
djack109

Reputation: 1377

Why should I use ILogger or Serilog?

As the question suggests, why should I use ILogger or Serilog or any other 3rd party logger for that matter. I have absolutely nothing against either or any 3rd party loggers. I've traditionally always rolled my own, I don't find it difficult or time consuming, more often than not I've just reused/rehashed something I've written before.

I'm not looking to bash anything. But from what I've read they pretty much do what my logger does and that's just simple messages and time stamps so I can see whats going on. I capture this

Date/Time
Message or error message
Module that added the log (name)
Logged in user (if my app has users)

I'm just looking to see what the community thinks

Upvotes: 1

Views: 889

Answers (1)

Daboul
Daboul

Reputation: 2733

For Serilog, I've recently been through a series of article that explains it fairly well: https://ranjeet.dev/All-about-structured-logging-introduction/

The main reason is to leverage structured logging, which consists in adding machine friendly meta data, on top of classical human friendly string based logging. When you end up with a big system in production, this is a gamer changer, because going through Gb of text files would be very unproductive. Then, on top of that, you get a very well thought framework with addins and integration to easily manipulate your logs.

Upvotes: 1

Related Questions