You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logging is currently done with log files using NLog. I propose that we switch to using console logging. It would also be preferable to have the logging configuration as a docker config in order to change the logging level at runtime. This way we don't have to re-deploy the web server just to change the log-level
The text was updated successfully, but these errors were encountered:
When you say "log level", that means "debug", "production" and similar? I can't imagine it will be important to switch between them runtime - or will it?
Another thing: "console loging" - that means output goes to the console, right? Isn't that awkward? (But of course: you don't have to get rid of old log files, and that is a pro..)
What does it cost resource-wise? Is it a big job to switch?
Logging is currently done with log files using NLog. I propose that we switch to using console logging. It would also be preferable to have the logging configuration as a docker config in order to change the logging level at runtime. This way we don't have to re-deploy the web server just to change the log-level
The text was updated successfully, but these errors were encountered: