This is an attempt at documenting page documents the available options for the service services the DAM center Center has in Dotnet Core. The services covered by this document are the services in the DigizuiteCore and the AutomationWorkflows folder“DigizuiteCore” and “AutomationWorkflows” folders.
Logging
The following keys are available in the “Logging” section of the appsettings.json.
All settings are reloaded on-the-fly if when the appsettings.json file is changed, . 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, but they can regardless of this, they may all be addedused.
Option name | Description | ||
|---|---|---|---|
| How much logging there should The amount of logging to be included. Valid values are:
with With each log level logging more informationhas more 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. | ||
| If the centralized logging mechanic should be enabled. This has to be enabled to be able to pull logs directly from Media Manager. |
| The path where the service should attempt to log it’s own logs if 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 done.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 should be enabled. The same warning as above applies. you have 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 Please be very cautious when enabling this, as it doesn’t clean up after itself. Once the service is up and running again, as it doesn’t clean up after itself, so it can risk filling the diskanew, 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.