This page aims to document documents the available options for the services the DAM center Center has in Dotnet Core. The services are in the “DigizuiteCore” and “AutomationWorkflows” folders.
...
All settings are reloaded on-the-fly when the appsettings.json file is changed, i. I.e there is no need to restart the processthe processes. You need, however, to have the entire path to the log file (sans the log file) pre-created upon load. This typically is only an issue for when you change the log path.
The following keys are available in the “Logging” section of the appsettings.json.
Some of these settings might not be visible by default, howeverregardless of this, they can may all be used still.
Option name | Description | ||
|---|---|---|---|
| The amount of logging to be included. Valid values are:
With each log level logging has more information info than the former (including 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 - the following:
Reduces 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 providedset at the same time. | ||
| 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. By enabling this, you give access for people to look at the logs though MM |
| (Requires The path provided here will be used for local logging. Please note that: 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. Setting this to a folder that doesn’t exist upon load, will make both Centralized+local logging not work (the logs will be blank both places) | ||
| If “local logging” you have Both this and |
...
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 if not disabled again.
Log server configuration
The log server has the following configuration options:
Option name | Description |
|---|---|
| The location of the log files on disk (Can be either a relative or absolute path) |
| The size in MB that determines (roughly) how big each log file should be allowed to become |
| Determines how many old log files can be at the same time |
| Determines how long we should keep error logs |
| Determines how often the cleanup of error logs is run |
| Determines what kind of storage to use. Currently, only “Local” is supported. |
| The number of log messages to keep in memory when looking for related log lines when an error is logged. Decreases memory usage. The default setting determines it to keep around 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.