[
https://issues.apache.org/jira/browse/KNOX-3063?focusedWorklogId=933766&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-933766
]
ASF GitHub Bot logged work on KNOX-3063:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Sep/24 08:24
Start Date: 09/Sep/24 08:24
Worklog Time Spent: 10m
Work Description: hanicz opened a new pull request, #934:
URL: https://github.com/apache/knox/pull/934
## What changes were proposed in this pull request?
Added monitorInterval property to the Configuration tag in the log4j2
configuration file. With this change Knox can change log level at runtime there
is no need to restart the service.
## How was this patch tested?
Ran existing tests locally.
Tested the new behaviour locally by changing the knox.gateway log level to
TRACE and checking the gateway.log file for DEBUG and TRACE level logs.
Issue Time Tracking
-------------------
Worklog Id: (was: 933766)
Remaining Estimate: 0h
Time Spent: 10m
> Add monitorInterval property to log4j2 configuration file
> ---------------------------------------------------------
>
> Key: KNOX-3063
> URL: https://issues.apache.org/jira/browse/KNOX-3063
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 2.1.0
> Reporter: Tamás Hanicz
> Priority: Minor
> Fix For: 2.1.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> By adding the monitorInterval property to the log4j2 configuration file the
> users are able to change the log level runtime. There is no need to restart
> Knox with if this change is present.
> {code:java}
> <Configuration monitorInterval="15"> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
