[
https://issues.apache.org/jira/browse/UNOMI-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757312#comment-17757312
]
David Griffon commented on UNOMI-796:
-------------------------------------
Properties added.
>From now on, env variable {{UNOMI_LOGS_JSONSCHEMA_LEVEL}} allows to set log
>level for JSON Schema
> Add log4j conf + env variable to set SchemaService log level
> ------------------------------------------------------------
>
> Key: UNOMI-796
> URL: https://issues.apache.org/jira/browse/UNOMI-796
> Project: Apache Unomi
> Issue Type: Bug
> Reporter: Kevan Jahanshahi
> Assignee: David Griffon
> Priority: Major
> Fix For: unomi-2.4.0
>
>
> The idea is to be able to configure easily the LOG LEVEL of package:
> *org.apache.unomi.schema.impl*
>
> In case people experience trouble with schema validation, it would be require
> to switch this log to *DEBUG* to have real informations.
>
> the file to modify is:
> [https://github.com/apache/unomi/blob/master/package/src/main/resources/etc/org.ops4j.pax.logging.cfg]
>
> Like for cxf example in same file:
> {code:java}
> log4j2.logger.cxfInterceptor.name = org.apache.cxf.interceptor
> log4j2.logger.cxfInterceptor.level = ${org.apache.unomi.logs.cxf.level:-WARN}
> {code}
> associated to env (custom.system.properties):
> {code:java}
> org.apache.unomi.logs.cxf.level=${env:UNOMI_LOGS_CXF_LEVEL:-WARN} {code}
>
> Do something like this:
> {code:java}
> log4j2.logger.jsonSchema.name = org.apache.unomi.schema.impl
> log4j2.logger.jsonSchema.level =
> ${org.apache.unomi.logs.jsonschema.level:-INFO} {code}
> to be associated env variable (custom.system.properties):
> {code:java}
> org.apache.unomi.logs.jsonschema.level=${env:UNOMI_LOGS_JSONSCHEMA_LEVEL:-INFO}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)