Logging

previous  Top  next

Quality assurance and quality control were the focus of considerations when developing Untis 2020. Therefore many improvements have been made which can only be seen in rare cases on the surface and which you as a user will never or only rarely get in contact with, e.g. when you have technical problems. One of these improvements is a standardised logging in Untis 2020.

 

 

 

20U_001

 

The different logfiles were standardised at a central point, i.e. in '%APPDATA%\gp-Untis\logs\' in a global logfile. A new logfile is created per day.

 

As soon as there are 31 logfiles the oldest is always deleted. The Logging Level range from 0 - Verbose , über 1 - Debug and 2 - Information , 3 - Warning , and 4 - Error to 5 - Fatal .

 

Generally speaking this means that a lower logging level stands for a more refined granularity in its output. We recommend to set the LogLevel to '2 - Information' and to change it only when you have a problem and a (support) team member of Untis GmbH or a Untis partner asks you to. The log files are automatically included in the support data as of Untis 2020.

 

If you are interested in the technical part of it, find in the following a short description of the individual log levels (Source: https://github.com/serilog/serilog/wiki/Writing-Log-Events [abgerufen am 5.4.2019, 14:30])

Verbose

tracing information and debugging minutiae; generally only switched on in unusual situations

Debug

internal control flow and diagnostic state dumps to facilitate pinpointing of recognised problems

Information

events of interest or that have relevance to outside observers; the default enabled minimum logging level

Warning

indicators of possible issues or service/functionality degradation

Error

indicating a failure within the application or connected system

Fatal

critical errors causing complete failure of the application