Differences

This shows you the differences between two versions of the page.

--- devel:documentation:application_configuration:dev:backend [2020/04/06 10:33]
tomiskar [Attachment storage]
+++ devel:documentation:application_configuration:dev:backend [2020/04/08 09:41]
tomiskar [Logger]
@@ Line 214: / Line 214: @@
 ''DefaultAttachmentManager'' stores binary files on file system. Binary files can be attached to any entity, which implements ''AttachableEntity'' interface, [[..:..:modules_rpt:dev:attachment_manager| read more]].
-In the application profile (application.properties).
+In the application profile (application.properties):
 <code properties>
@@ Line 224: / Line 224: @@
 </code>
-In the application profile (application.properties) and overloadable via ''ConfigurationService''.
+In the application profile (application.properties) and overloadable via ''ConfigurationService'':
 <code properties>
@@ Line 864: / Line 864: @@
 ==== Logger ====
-In the application profile (''application.properties'') - overloadable via ''ConfigurationService''.
+In the application profile (''application.properties''):.
+<code properties>
+# Show thread name configured by thread pools (task, event) in logs (generated name is shown otherwise)
+# Two appenders 'console' and 'file' are provided by product. Same configuration is needed for your custom appenders (added in logback.xml).
+logging.pattern.console=%d{yyyy-MM-dd HH:mm:ss.SSS} %5level %relative --- [%thread] %logger{36}.%M : %msg%n
+logging.pattern.file=%d{yyyy-MM-dd HH:mm:ss.SSS} %5level %relative --- [%thread] %logger{36}.%M : %msg%n
+</code>
 Logger levels can be configured programmatically (override ''logback.xml'' file with default logger levels configuration).
+In the application profile (''application.properties'') - overloadable via ''ConfigurationService'':
 <code properties>