DEBUG severity log messages are not showing up in the log - Githubissues

avioconsulting / mule-custom-logger

Custom Mule logger to replace MuleSoft's out of the box logger. Use log4j2 layouts to convert log messages to JSON etc.

BSD 2-Clause "Simplified" License

13 stars 18 forks source link

DEBUG severity log messages are not showing up in the log #47

Closed ghughlett closed 1 year ago

ghughlett commented 1 year ago

Using version 2.0.1 of logger from Maven Central.

The avio-logger-config has a default Log Category of ${log.cat}
The log4j2.xml has an asyncLogger defined of ""
The flow start and end loggers are using DEBUG severity

When a request is run, only INFO messages for that log category appear in the output.

Attaching three files:

log-output-debug.txt which has the flow log output with DEBUG severity defined.
log-output-info.txt which shows the flow log output with INFO severity defined.
log4j2.xml file (added .txt extension because GitHub doesn't support XML)

log4j2-xml.txt log-output-debug.txt log-output-info.txt

tannersherman commented 1 year ago

Closing this as was determined to be a configuration issue within the MuleSoft application. Used this MuleSoft help article to aid in resolution: https://help.mulesoft.com/s/article/How-to-use-properties-in-log4j2-Configuration-File