[
https://issues.apache.org/jira/browse/ARTEMIS-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744275#comment-17744275
]
Robbie Gemmell commented on ARTEMIS-4367:
-----------------------------------------
An approach I've seen used elsewhere is having such 'operational messages'
given individual loggers in a hierarchy. That way they can all be configured
'as a whole' typically (often not configured specifically at all, just using
the parent or root level logger config)...but can also still be configured very
granularly if needed (i.e per message) as they also had their own log category.
In this case each existing 'IDd message' has a unique code, and currently they
all use a specific logger category, e.g 'the client logger' or 'the server
logger' or 'journal logger'. Since all the logging stuff for these is
generated, they could easily use a sub-category generated based on the code. I
guess one consideration would be, how many of them are there, and would that be
an issue. On the other side of that though, consider that outside of these
specific 'IDd logger classes', every single implementation class with any
logging has its own logger.
> Split server logger codes into advice and info category and by logger
> ---------------------------------------------------------------------
>
> Key: ARTEMIS-4367
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4367
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.29.0
> Reporter: Gary Tully
> Priority: Major
>
> We have server logger that uses AMQXXX codes for log messages. all is good.
> We have a class of log message that is advice...
> * address X does not a DLQ registered
> * address X does not an expiry address registered
> These advice are info or warn trying to help users but often times the config
> is by design and this advice is just noise. Users want to disable, but not
> all of the server logger infor or warn messages.
> log4j allows to filter, but that is expensive.
> If we split out these advice messages into a separate class and use a nested
> logger per code, it would be simple to suppress advice that is noise for a
> given scenario
> There was an new advice in ARTEMIS-4362 that suggests we do have a class of
> advices/warns that would benefit from a simple way to suppress.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
