Differences
This shows you the differences between the selected revisions of the page.
| ui_pref_logging 2017-06-01 | ui_pref_logging 2023-11-22 (current) | ||
| Line 1: | Line 1: | ||
| - | ====== Logging Page (Preferences Dialog) ====== | + | ====== The Logging Page (Preferences Dialog) ====== |
| The //Logging page// on the [[ui_preferences|Preferences dialog]] allows user to configure [[logging|session and XML logging]]. | The //Logging page// on the [[ui_preferences|Preferences dialog]] allows user to configure [[logging|session and XML logging]]. | ||
| Line 7: | Line 7: | ||
| ===== [[session_log]] Session log ===== | ===== [[session_log]] Session log ===== | ||
| - | To enable session log, check //Enable session logging on level//. | + | To enable logging to a file, check //Enable session logging on level//. |
| - | To increase verbosity of the session log select //Debug 1// or //Debug 2// level. You will probably need these (together with logging to file), when [[reporting|reporting bugs]] only. | + | To increase a verbosity of the session log, select //Debug 1// or //Debug 2// level. You will probably need these (together with a logging to file), when [[reporting|reporting bugs]] only. The //Debug 2// level can significantly deteriorate performace. To decrease a verbosity of the session log, select //Reduced// level. |
| - | To enable logging to file tick //Log to file// checkbox and specify [[local_path|local path]] to log file. Log file name can contain following patterns: ''!Y'' (year), ''!M'' (month), ''!D'' (day), ''!T'' (time), ''!@'' (hostname), ''!S'' (session name), ''!P'' (process ID), ''!!'' (exclamation mark). | + | Specify [[local_path|local path]] to log file into //Log path// box. Log file name can contain following patterns: ''!Y'' (year), ''!M'' (month), ''!D'' (day), ''!T'' (time), ''!@'' (hostname), ''!S'' (session name), ''!P'' (process ID), ''!!'' (exclamation mark). |
| If you select //Append// option, and the logging file already exists, session log will be appended to the end of the file. Otherwise the existing file will be overwritten. | If you select //Append// option, and the logging file already exists, session log will be appended to the end of the file. Otherwise the existing file will be overwritten. | ||
| + | |||
| + | You can limit a log file size by specifying a maximum size in bytes in //Rotate log files after reaching// box. Supported units are ''K'', ''M'' and ''G''. If a log file reaches the configured limit, it is archived to a file with extension ''.1'', ''.2'', etc. You can limit number of archived log files using //Delete old logs files, keep ... files// checkbox. | ||
| If you enable logging to file in mid-session the past events will not be written to the log retrospectively. Note that to log several sessions simultaneously to file, you need to ensure unique names of the log files (e.g. using some of the patterns above). Passwords are not written to log file. | If you enable logging to file in mid-session the past events will not be written to the log retrospectively. Note that to log several sessions simultaneously to file, you need to ensure unique names of the log files (e.g. using some of the patterns above). Passwords are not written to log file. | ||
| - | Tick //Log passwords and other sensitive information// to turn off obfuscation of passwords and other sensitive information in session log. It is useful when debugging authentication issues. Note that sensitive information passed on [[commandline|command-line]] are logged even with the option turned off. | + | Tick //Log passwords and other sensitive information// to turn off obfuscation of passwords and other sensitive information in session log. It is useful when debugging authentication issues. |
| - | ===== XML log ===== | + | ===== [[xml]] XML log ===== |
| To enable [[logging_xml|XML log]], check //Enable XML logging to file// and specify [[local_path|local path]] to log file. You can use the same patterns as for session log file (see above). | To enable [[logging_xml|XML log]], check //Enable XML logging to file// and specify [[local_path|local path]] to log file. You can use the same patterns as for session log file (see above). | ||