...
Basic Class Architecture
Logger itself
Debug LevelsDebugLevels
The following levels are defined as class constants prefixed with LEVEL_ in ZfExtended_Logger class:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
resources.ZfExtended_Resource_Logger.writer.default.type = 'ErrorLog' resources.ZfExtended_Resource_Logger.writer.default.filter[] = "level <= debug" ; → warn logs from fatal to debug ; Test config: resources.ZfExtended_Resource_Logger.writer.mail.type = 'DirectMail' ; via the formatter define what the user gets: full debug content, or only notice and so on. resources.ZfExtended_Resource_Logger.writer.mail.filter[] = "level <= error" ; → warn logs from fatal till error resources.ZfExtended_Resource_Logger.writer.sender = 'sysadmin@example.com' ; → should be overwritten with useful values in installation.ini resources.ZfExtended_Resource_Logger.writer.mail.receiver[] = 'sysadmin@example.com' ; → should be overwritten with useful values in installation.ini resources.ZfExtended_Resource_Logger.writer.mail.receiver[] = 'other-important-person@example.com' ; → should be overwritten with useful values in installation.ini resources.ZfExtended_Resource_Logger.writer.mail.type = 'Database' ; via the formatter define what the user gets: full debug content, or only notice and so on. resources.ZfExtended_Resource_Logger.writer.mail.filter[] = "level <= debug" ; logs from fatal to debug |
...
In the following table a list of valid keywords and operands is listed:
| Keyword | Valid Operands | Description | |
|---|---|---|---|
| level | <= >= = | Is used to compare with the log levels as defined at the top of this page. The second operand must be a valid log level: "fatal", "error", "warn" etc. | |
| origin | = ^= $= *= | The origin of the event must be matched either completely, or just a part of the string, as defined by the usable string operators. | |
| exception | = *= | The exception equals (= operator) the given exception class name, or the current exception is a subclass of the given exception name (*= operator). |
Logging Database Tables
Currently there are two database tables receiving events:
...