Changes between Version 23 and Version 24 of TracLogging
- Timestamp:
- Mar 6, 2022, 9:01:02 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracLogging
v23 v24 19 19 == Log Levels 20 20 21 The verbosity level of logged messages can be set using the [TracIni#logging-log_level-option "[logging] log_level"] option. The log level defines the minimum level of urgency required for a message to be logged , and those levels are:21 The verbosity level of logged messages can be set using the [TracIni#logging-log_level-option "[logging] log_level"] option. The log level defines the minimum level of urgency required for a message to be logged: 22 22 23 23 '''CRITICAL''':: Log only the most critical (typically fatal) errors. … … 27 27 '''DEBUG''':: Trace messages, profiling, etc. 28 28 29 Additionally, you can 29 Additionally, you can enable logging of SQL statements at debug level. This is turned off by default, as it's very verbose. Set [TracIni#trac-debug_sql-option "[trac] debug_sql = yes"] to activate. 30 30 31 31 == Log Format … … 43 43 }}} 44 44 45 In a multi-project environment where all logs are sent to the same place (e.g. `syslog`), it makes sense to add the project name. In this example we use `basename` sincethat can generally be used to identify a project:45 In a multi-project environment where all logs are sent to the same place (e.g. `syslog`), it makes sense to add the project name. In this example we use `basename` as that can generally be used to identify a project: 46 46 {{{#!ini 47 47 log_format = Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s