Database logger for ASP.NET Core
Should I hide exceptions or let them propagate? Logging should be redundant in production environment, so I think hiding them would be fine.


Both. I think this should be configurable. During setup / testing exceptions should be thrown for easier debugging (database permission issues etc.) but in production exceptions should not be thrown.

I have been using NLog and at least in my use this way has been working fine.