21 | | レベルの種類: |
22 | | '''CRITICAL''':: 最も危険なログのみ。たいていは致命的なメッセージです。 |
23 | | '''ERROR''':: 処理失敗、バグ、エラーの要求。 |
24 | | '''WARN''':: 警告、処理を中断するほどではないイベント。 |
25 | | '''INFO''':: 診断メッセージ。すべてのプロセスについてのログ情報。 |
26 | | '''DEBUG''':: トレースメッセージ、プロファイリングなど。 |
| 20 | The verbosity level of logged messages can be set using the `log_level` option in [wiki:TracIni#logging-section trac.ini]. The log level defines the minimum level of urgency required for a message to be logged, and those levels are: |
| 21 | |
| 22 | '''CRITICAL''':: Log only the most critical (typically fatal) errors. |
| 23 | '''ERROR''':: Log failures, bugs and errors. |
| 24 | '''WARN''':: Log warnings, non-interrupting events. |
| 25 | '''INFO''':: Diagnostic information, log information about all processing. |
| 26 | '''DEBUG''':: Trace messages, profiling, etc. |
| 27 | |
| 28 | Note that starting with Trac 0.11.5 you can in addition enable logging of SQL statements, at debug level. This is turned off by default, as it's very verbose (set `[trac] debug_sql = yes` in TracIni to activate). |
| 29 | |
| 30 | == Log Format == |
| 31 | |
| 32 | Starting with Trac 0.10.4 (see [trac:#2844 #2844]), it is possible to set the output format for log entries. This can be done through the `log_format` option in [wiki:TracIni#logging-section trac.ini]. The format is a string which can contain any of the [http://docs.python.org/lib/node422.html Python logging Formatter variables]. Additonally, the following Trac-specific variables can be used: |
| 33 | '''$(basename)s''':: The last path component of the current environment. |
| 34 | '''$(path)s''':: The absolute path for the current environment. |
| 35 | '''$(project)s''':: The originating project's name. |
| 36 | |
| 37 | Note that variables are identified using a dollar sign (`$(...)s`) instead of percent sign (`%(...)s`). |
| 38 | |
| 39 | The default format is: |
| 40 | {{{ |
| 41 | log_format = Trac[$(module)s] $(levelname)s: $(message)s |
| 42 | }}} |
| 43 | |
| 44 | 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: |
| 45 | {{{ |
| 46 | log_format = Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s |
| 47 | }}} |