-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: what changes are honored with reloadOnChange? #154
Comments
Hi , If I remember properly, the only changes that can be honored are the ones related to Lines 126 to 143 in 71ee59d
A logging pipeline is "immutable by design" once it has been created, so it can no longer be altered. The only parts of the logging pipeline that support some sort of dynamic updates are the level, the same way you would work with a I thinks we were mentioning some doubts about that part here as well : #99 |
Tracked until we have updated documentation. |
Is there an example of how to make config reloading work? I downloaded the sample and changes to the minimumLevel in the config file don't seem to take effect without restarting the app. |
Hi, @andyvig , make sure you pass Changes to top-level |
Documentation was updated |
I've basically copied your sample, so I am using almost the exact same configuration you have specified in your appsettings.json (except I put the log files somewhere else). I tried changing the path to my log file - the one in Async-File from .\Logs\serilog-configuration-sample.txt to .\Logs\MyLogs\serilog-configuration-sample.txt but that change was not picked up, and I only have the one log file in .\Logs.
I also tried changing the outputTemplate, but that change was not picked up either.
I am using this in asp.net core.
The text was updated successfully, but these errors were encountered: