Changes between Version 8 and Version 9 of TracLogging

Timestamp:

22/02/2023 10:14:50 (21 months ago)

Author:

trac

Comment:

--

TracLogging

@@ -18 +18 @@
 == Log Levels
 
-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:
+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:
 
  '''CRITICAL''':: Log only the most critical (typically fatal) errors.
@@ -26 +26 @@
  '''DEBUG''':: Trace messages, profiling, etc.
 
-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.
+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.
 
 == Log Format
@@ -42 +42 @@
 }}}
 
-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` since that can generally be used to identify a project:
+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:
 {{{#!ini
 log_format = Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s