Page History
...
| Warning | ||
|---|---|---|
| ||
Setting the log level to DEBUG or TRACE will generate a lot of logging data. This is not recommended in a production environment, unless absolutely necessary. Make sure enough disk space is available for the log file(s). |
Logging Pattern
The pattern in the log4j.xml defines what information is logged. Log4j supports a number of lookups, Servoy has added servoy-lookup (starting from release 2021.06) that can be used to print Servoy-specific data in the logfile.
The lookup is called servoy and can be used like in this example. Note that the double dollar-sign is needed to ensure that the value is looked up for each message, otherwise Log4j may cache the value.
| Code Block |
|---|
<PatternLayout
pattern="%d %p [%t] %c - %m [$${servoy:clientid:-(NO CLIENT)} $${servoy:solution:-(NO SOLUTION)}]%n" /> |
The supported lookup keys are:
- clientid
- solution
- username
- useruuid
- clienttype
- hostname
- hostaddress
- sessionkey (ng client only)
| Note | ||
|---|---|---|
| ||
For more information on log4j, visit the Log4j site (Frequently Asked Log4j Questions section can help with some questions). |
...
Overview
Content Tools
Activity