Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-4367

Split server logger codes into advice and info category and by logger

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.29.0
    • None
    • Broker
    • None

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            gtully Gary Tully
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: