Project

General

Profile

Actions

Task #2203

closed

Configure pattern for logback - server configuration documentation

Added by Radek Tomiška about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Petr Fišer
Category:
Infrastructure
Target version:
-
Start date:
04/09/2020
Due date:
% Done:

0%

Estimated time:
Owner:

Description

In related ticket #2193 was improved product documentation about using correct thread name in logs:
https://wiki.czechidm.com/devel/documentation/application_configuration/dev/backend#logger

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

I'm not sure, if different appenders are used for production or instalation guide (database appender doesn't need pattern). If appenders are the same ('console', 'file'), then no additional configuration is needed (default is in product) and this ticket can be closed.
Could you check please server documentation for logback and used appenders?


Related issues

Related to IdStory Identity Manager - Defect #2193: LRT: configure logback to show configured thread name in logsClosedRadek Tomiška04/07/2020

Actions
Actions #1

Updated by Radek Tomiška about 4 years ago

  • Related to Defect #2193: LRT: configure logback to show configured thread name in logs added
Actions #2

Updated by Petr Fišer about 4 years ago

IIRC we do not set this explicitly anywhere in server deployment HOWTOs so everything should be fine.
I will take a look and update HOWTOs if necessary.

Actions #3

Updated by Petr Fišer about 4 years ago

  • Status changed from New to Resolved

We do not override logging.pattern.* settings anywhere so the default application.properties configuration is sufficient.
Also, we use only DB / file appenders. In containers we log onto console so all cases are covered.

For project deployments, we do not need to change anything anywhere.

Actions #4

Updated by Petr Fišer about 4 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF