...
Ubisecure CustomerID logging behaviour is configured via WildFly. Please see instructions from WildFly documentation. The default log settings generated to the standalone.xml
file look like this:
Code Block | ||||
---|---|---|---|---|
| ||||
<subsystem xmlns="urn:jboss:domain:logging:3.0"> ... <periodic-rotating-file-handler name="CID_AUDIT_LOG_FILE_HANDLER" autoflush="true"> <level name="INFO"/> <formatter> <named-formatter name="AUDIT-PATTERN"/> </formatter> <file relative-to="jboss.server.log.dir" path="customerid_audit.log"/> <suffix value=".yyyy-MM-dd"/> <append value="true"/> </periodic-rotating-file-handler> <periodic-rotating-file-handler name="CID_DIAG_LOG_FILE_HANDLER" autoflush="true"> <level name="INFO"/> <formatter> <named-formatter name="PATTERN"/> </formatter> <file relative-to="jboss.server.log.dir" path="customerid_diag.log"/> <suffix value=".yyyy-MM-dd"/> <append value="true"/> </periodic-rotating-file-handler> ... <logger category="com.ubisecure.customerid.log.audit" use-parent-handlers="false"> <level name="INFO"/> <handlers> <handler name="CID_AUDIT_LOG_FILE_HANDLER"/> </handlers> </logger> <logger category="com.ubisecure" use-parent-handlers="false"> <level name="INFO"/> <handlers> <handler name="CID_DIAG_LOG_FILE_HANDLER"/> </handlers> </logger> <logger category="org.apache.wicket"> <level name="INFO"/> </logger> ... <formatter name="PATTERN"> <pattern-formatter pattern="%d;%-5p;node1;%t;%c;%s;%E%n"/> </formatter> <formatter name="AUDIT-PATTERN"> <pattern-formatter pattern="%d;%s%n"/> </formatter> ... </subsystem> |
...