Installing : Installing the UNICOM Digital Transformation Toolkit : Licensing UNICOM Digital Transformation Toolkit : Monitoring errors and generating diagnostic information
  
Monitoring errors and generating diagnostic information
The License Server records errors, server start events, and server stop events in a file called ult_licesrv.log in its working directory.
To change the logfile name and location
See Logfile=filename.
To get more detailed information
Change the Level parameter in the configuration file. You can change this parameter without having to restart the License Server.
To log significant diagnostic events, such as changes to licensed usage, use:
[Logging]
Logfile=ult_licesrv.log
Level=2
COMLevel=1
COMLevel=1 reduces the logged events from the TCP/IP comms subsystem.
To log all diagnostic information, including session heartbeat traffic, and so on, use:
[Logging]
Logfile=ult_licesrv.log
Level=3
Diagnostic events are written to separate files from the main error log, so they can be deleted without losing important error information. The diagnostic logfile is in the same location as the main error log, and has diag_ at the start of its name, for example: diag_ult_licesrv.log.
To prevent the diagnostic logfile from becoming too big, it is automatically broken up every hour; the previous hour’s content is put into a GZip file, with the date and time appended, for example: diag_ult_licesrv_20151204_170000.log.gz
Diagnostic log files older than 72 hours are deleted automatically.
See also
Licensing UNICOM Digital Transformation Toolkit