[MAGNOLIA-8316] Could this log be lowered? Created: 22/Feb/22  Updated: 20/Jul/22  Resolved: 21/Apr/22

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.19

Type: Improvement Priority: Neutral
Reporter: Michiel Meeuwissen Assignee: Fernando Cherchi
Resolution: Fixed Votes: 0
Labels: VN-Testing, nucleus
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Nucleus Quality Maintenance
Sprint: Nucleus 8
Story Points: 1
Team: Nucleus

 Description   

In info.magnolia.importexport.BootstrapUtil we'll find this line:

log.warn("Deleted already existing node for bootstrapping: {}", fullPath);

This happens on every update, I'd rather have it on info.

The only thing I can think of is simply set the logging level to ERROR for this class, to avoid having warnings in the log. I think it is useful information though, but I doubt whether it warrants a warning, this is basically just normal flow.



 Comments   
Comment by Jaromir Sarf [ 02/Mar/22 ]

Discovery completed

While bootstraping already imported node is deleted, message about deletion is logged as warning.

Quickfix:

Change warning to info or debug.
From

log.warn("Deleted already existing node for bootstrapping: {}", fullPath); 

to

log.info("Deleted already existing node for bootstrapping: {}", fullPath);
Comment by Michiel Meeuwissen [ 04/Mar/22 ]

Thank you for the recapitulation of the issue. That's indeed how I did propose changing it. The question is though : do you agree?

Comment by Jaromir Sarf [ 04/Mar/22 ]

Yes, we agree with the solution. We use discovery notes to sum up the issue and to make it easier to estimate.  

Comment by Fernando Cherchi [ 21/Apr/22 ]

Ported to Cloud

Generated at Mon Feb 12 04:31:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.