...
All settings are reloaded on-the-fly when the appsettings.json file is changed, i.e there is no need to restart the process.
Some of these settings might not be visible by default, still, but they can all of them can be addedused.
Option name | Description | ||
|---|---|---|---|
| The amount of logging to be included. Valid values are:
With each level logging more information than the former. | ||
| A dictionary that can be used to change the log level of certain namespaces. Usually not something you need to change. For example:
Reduces the LogLevel of Entity Framework to Warning, rather than the normal log level set for the rest of the service. Multiple keys can be provided. | ||
| When the centralized logging mechanic should be enabled. This has to be enabled in order to be able to pull logs directly from the Media Manager. | ||
| The path where the service should attempt to log its own logs when “local logging” is enabled. This does not clean up after itself, so this should only be enabled for the sake of debugging, and should be turned off once finished. | ||
| If “local logging” is enabled. The same warning as above applies. Both this and |
Note
There are certain may be times when the one or more applications fail to start completely (Usually fully start. This is usually due to some problem an issue with the environment), in this case. In case of this happening, it can may be useful to go into access the failing services' Web.Config file for the servicefiles, and enable stdout logging. One should be careful to disable this, once the service is up and running againPlease be very cautious when enabling this, as it doesn’t clean up after itself, so it can risk . Once the service is up and running anew, there’s a real threat of it filling the disk entirely.