Won't Do
Details
Details
Assignee
Unassigned
UnassignedReporter
Oleksii Petrenko
Oleksii PetrenkoLabels
Priority
Development Team
Spitfire
Release
Orchid (R1 2023)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 15, 2022 at 2:55 PM
Updated March 30, 2023 at 12:00 PM
Resolved October 12, 2022 at 11:26 PM
Purpose/Overview:
Logging should be improved for more productive troubleshooting.
Requirements/Scope:
Check that log4j2.properties doesn't exist or it is aligned with https://folio-org.atlassian.net/wiki/display/DD/Folio+logging+solution
The logging commands of the module should be adjusted according to the document: https://folio-org.atlassian.net/wiki/display/DD/Logging (hereinafter doc.), including the following aspects:
Log message must be informative and contain business parameters/indicators (see doc. p. 1.1)
Logging of import business logic actions and steps (see doc. p. 1.2)
Logging of any edge cases scenarios and essential conditional business logic paths (see doc. p. 1.3)
Logging of all exceptional cases (see doc. p. 1.4)
Avoid logging sensitive information or use a specific method of Folio Spring Base to produce messages (see doc. p. 3)
Add step "Check logging" to PULL_REQUEST_TEMPLATE.md
AС
The property file and all logging commands are adjusted.