mardi 3 mars 2015

Loggers - Functional, non-functional or layered?


We use different loggers to break up and apply specific rules to different kinds of log data. We typically specify which logger to be used with something like this:



var logger = Logger.GetLogger("MyLogger");


What is a recommended strategy on loggers?



  • Functional: For example, "Sales", "Administration", "Orders", etc.

  • Non-functional: For example, "Performance", "Caching", "Authentication", etc.

  • Layered: For example, "DAL", "Models", "Infrastructure", "BLL", etc.

  • Classes: For example, "OrderRepository", "OrdersController", etc.


I have often see the use of class names, but surely this is too granular?





Aucun commentaire:

Enregistrer un commentaire