Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Default log configuration is way too verbose

Description

The default log4j2.properties file has everything turned up to the DEBUG level. This may be useful for development but it is impossible for production. It appears this was set as part of the work for , and it has made its way into all the latest releases of mod-source-record-manager.

Of course this can be tuned manually by operators, but it was an unpleasant surprise to find the logs so noisy by default.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

Operators can mount a custom log4j.properties file and point to it with the log4j.configurationFile system property.

Attachments

2

Checklist

hide

TestRail: Results

Activity

Show:

Aliaksandr FedasiukOctober 26, 2023 at 2:33 PM
Edited

Tested on Poppy bf. Log attached.

Oleksii PetrenkoOctober 24, 2023 at 4:00 PM

Deployed to Poppy bf env. Please proceed with verification

Aliaksandr FedasiukOctober 20, 2023 at 12:04 PM

The number of DEBUG messages has been significantly reduced.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Folijet

Parent

Fix versions

Release

Poppy (R2 2023) Bug Fix

RCA Group

Implementation coding issue

Affected releases

Poppy (R2 2023)
Orchid (R1 2023)

Affected Institution

!!!ALL!!!

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created October 18, 2023 at 7:21 PM
Updated October 28, 2023 at 10:48 AM
Resolved October 20, 2023 at 12:06 PM
TestRail: Cases
TestRail: Runs