...
System-Admins should add their custom writer configuration to the installation.ini.
Please see ErrorHandling and Application Logger for information about the log levels.
The configuration in application.ini is reserved to translate5 developers - since this file is overwritten on each update.
...
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. Example: given FATAL(1), configured "level <= WARN(4)" the event is filtered, since level 1 (fatal) is lesser then level 4 (warn) |
| <= | Is true if the current level is equal or has a higher severity as the configured one. | |
| >= | Is true if the current level is equal or has a lower severity as the configured one. | |
| domain | = | The domain (origin) of the event must be matched completely. |
| != | The domain (origin) must not be equal to the configured one. | |
| ^= | The domain (origin) must start with the configured string. | |
| $= | The domain (origin) must end with the configured string. | |
| *= | The domain (origin) must contain the configured string. | |
| exception | = | The exception equals the given exception class name |
| != | The exception is different to the given exception class name | |
| *= | The current exception is a subclass of the given exception name |