[
https://issues.apache.org/jira/browse/ARTEMIS-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-4367:
--------------------------------
Issue Type: Improvement (was: Bug)
> 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 AMQ-6854 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)
