Skip to:

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

Reduce/Remove Ineffective Log Lines

Description

The log lines below can represent more than 50% of logs in mod-circulation for a duration of time. The log lines don’t have correlation id or any other tracking information, can contain PII & increase hosting costs for FOLIO by thousands of dollars.

  • [] [] [] [] INFO LoanRepresentation extendedLoan:: extendedLoan-2 is not <value>

  • [] [] [] [] INFO ummaryRepresentation createItemSummary:: createItemSummary-2 is not <value>

  • [] [] [] [] INFO ummaryRepresentation createItemSummary:: item.getStatus().getDate() is not <value>

  • [] [] [] [] INFO LoanRepresentation additionalPatronGroupProperties:: patronGroupAtCheckout is <value>

  • ⁃ [] [] [] [] INFO onentsRepresentation createCallNumberComponents:: result {"callNumber":"callNumber"-2}

Remove the log lines above and similar lines in the java classes from the INFO log level.

Environment

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Olamide Kolawole March 18, 2025 at 1:23 PM

Sort of related. The main driver with this story is to reduce the amount of logs generated by mod-circulation. That feature’s main concern is sensitive data in the logs.

Khalilah Gambrell March 18, 2025 at 1:08 PM

Thanks . How does this issue relate to this feature https://folio-org.atlassian.net/browse/UXPROD-5141?

Olamide Kolawole March 18, 2025 at 12:57 PM

This is high priority due to cost/security implications. We would like it sooner. From the dev side, I expect this to be very low effort.

Khalilah Gambrell March 14, 2025 at 6:27 PM

Hey - what is the priority of this issue? And is it okay that this work is not done until Trillium release?

Details

Assignee

Reporter

Priority

Development Team

Vega

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 5, 2025 at 8:42 PM
Updated last week
TestRail: Cases
TestRail: Runs