This page aims to document the available options for the services the DAM center has in Dotnet Core. The services are in the “DigizuiteCore” and “AutomationWorkflows” folders.
Logging
All settings are reloaded on-the-fly when the appsettings.json file is changed, i.e there is no need to restart the process.e
The following keys are available in the “Logging” section of the appsettings.json.
Some of these settings might not be visible by default, however, they can all be used still.
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 may be times when one or more applications fail to fully start. This is usually due to an issue with the environment. In case of this happening, it may be useful to access the failing services' Web.Config files, and enable stdout logging. Please be very cautious when enabling this, as it doesn’t clean up after itself. Once the service is up and running anew, there’s a real threat of it filling the disk entirely.
Log server configuration
The log server exposes the following configuration options:
Option name | Description |
|---|---|
| The location of the log files on disk (Can be either a relative path, or absolute) |
| The size on MB for now large each individual log file is allowed to be (Roughly) |
| How many log old log files we keep around |
| How long we should keep error logs |
| How often we should run cleanup of error logs |
| What kind of storage we should use. Currently on “Local” is supported. |
| The number of log messages to keep in memory when looking for related log lines when an error is logged. Decrease the decrease memory usage. The default setting should be able to keep about 100 MB of logs in memory (With some variance for the specific logs) |
All these settings can be changed on the fly, without requiring a restart of the LogServer process.