On ThinMan, the syslog connector is included in log4j2 but it has to be configured/personalized. The file path is ThinMan_install_dir\Server\webapps\ROOT\WEB-INF\classes\log4j2.xml (e.g. C:\Program Files\Praim\ThinMan\Server\webapps\ROOT\WEB-INF\classes\log4j2.xml)
For more information, refer to the page Log4j - Log4j 2 Appenders.
Here is an example of the configuration for syslog in log4j2.xml
....
<Appenders>
<Syslog name="syslog" format="RFC5424" host="10.2.10.26" port="514"
protocol="TCP" appName="thinman" includeMDC="true"
facility="LOCAL0" enterpriseNumber="18060" newLine="true"
immediateFail="true" messageId="Audit" id="App"/>
<RollingRandomAccessFile .... />
....
<Loggers>
<Root level="INFO">
<AppenderRef ref="MAIN" />
<AppenderRef ref="syslog" level="WARN"/>
</Root>
....
With this modification, all warning messages (or higher) are sent to a syslog service on port 514 at IP 10.2.10.26.
Depending on the type of syslog service contacted, only some of the declared attributes will be registered. For example, using a standard Linux syslogd daemon, in the log files produced, only appName is displayed, followed by the processId of the ThinMan Server."
Basic attributes to have a non-impacting behavior on thinman: name, format, host, port, protocol, appName, includeMDC=true, newLine=true, immediateFail=true
IMPORTANT!
Every time ThinMan server is updated, it is necessary to modify the log4j2.xml file, since it is rewritten during ThinMan upgrade.