Content Comparison

...

These Span and Trace IDs follows a standard from OpenTelemetry.

Changing the log level

Should more logging be required, then it is possible to increase and/or decrease the amount of information being written to disk. This follows the same pattern as always with the following posibilities:

• Trace

• Debug

• Information

• Warning

• Error

• Critical

• None

With Trace writing the most information and None writing (as the word suggest) nothing at all.

Each service has it’s own log file. For the Digizuite core services (i.e. everything in the webs in the folder /DigizuiteCore), we refer to the following documentation.

For the old code (DAM Center) there is a file in each folder called AppSettings.logging.json where the log level can be changed.

Please note this must be done for the service in question. Often times that means you should do it for the file in the folder /dmm3bwsv3, rather than the one in the root.

You can always figure out which folder it is needed in by following the path of the request.

For example a request looking like this

https://../dmm3bwsv3/SearchService.js?searchName=..

goes to the dmm3bwsv3 service and for that reason you must change the appsettings.logging.json file in the folder /dmm3bwsv3.

where as a request looking like this

https://../DigizuiteCore/LegacyService/api/metadata/editor

goes out to the LegacyService and as such must be changed in the appsettings.json file in the folder /DigizuiteCore/LegacyService.