[UXPROD-4097] Vega: Logging adjustment (NFR) - Poppy (extended) work Created: 27/Feb/23  Updated: 30/Nov/23  Resolved: 12/Oct/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)

Type: New Feature Priority: P2
Reporter: Stephanie Buck Assignee: Stephanie Buck
Resolution: Done Votes: 0
Labels: was-quesnelia-now-poppy
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-4384 Vega: Logging adjustment (NFR) - Ques... In Progress
Continues
continues UXPROD-3832 Vega: Logging adjustment (NFR) - Orch... Closed
Defines
is defined by CIRC-1809 Logging - circulation rules Closed
is defined by CIRC-1812 Logging - circulation resources Closed
is defined by CIRC-1881 Logging - circulation rules I-T Closed
is defined by MODTEMPENG-80 Logging improvement Closed
is defined by CIRC-1709 Logging improvement - enable request ... Closed
is defined by CIRC-1894 Logging - circulation resources: A - D Closed
is defined by CIRC-1895 Logging - circulation resources: E - N Closed
Release: Poppy (R2 2023)
Front End Estimate: Out of scope
Back End Estimate: XXXL: 30-45 days
Back-End Confidence factor: 80%
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R5

 Description   

Current situation or problem:
The logging is not sufficient for productive troubleshooting.

In scope
Improving of logging for modules according to the documentation (see Links to additional info).

Use case(s)
As a engineer I want to quickly find the root cause of the problem on environment using my log aggregation tool.

Proposed solution/stories
Stories are created for enhancement of logging for both Vert.x and Spring modules.

Links to additional info
https://folio-org.atlassian.net/wiki/display/DD/Logging
https://folio-org.atlassian.net/wiki/display/DD/Folio+logging+solution

Tasks linked to analyze existing logging in all modules.
Then if additional work required, created stories and estimate effort.


Generated at Fri Feb 09 00:37:15 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.