This is an attempt at documenting the available options for the service the DAM center has in Dotnet Core.
The services covered by this document are the services in the DigizuiteCore and the AutomationWorkflows folder.
Logging
The following keys are available in the “Logging” section of the appsettings.json.
All settings are reloaded on-the-fly when the appsettings.json file is changed, there is no need to restart the process.
Some of these settings might not be visible by default, but all of them can be added.
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: "Overrides": {
"Microsoft.EntityFrameworkCore": "Warning"
},
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 times when the applications fail to start completely (Usually due to some problem with the environment), in this case, it can be useful to go into the Web.Config file for the service, and enable stdout logging. One should be careful to disable this, once the service is up and running again, as it doesn’t clean up after itself, so it can risk filling the disk.