开启Log4j HTTP日志后日志被AWS HTTP调用淹没的解决方案咨询

Hey there, I’ve run into this exact issue before—when you enable Mule’s HTTP message logging, the AWS SDK’s verbose debug logs can quickly take over your log files. The good news is you can easily separate the two by adjusting your Log4j configuration to suppress the AWS debug logs while keeping the Mule HTTP logs you need.

Here’s how to do it: #

The key is to target the AWS SDK logger namespaces specifically and set their log level to something higher than DEBUG (like INFO or WARN). Since your existing config uses AsyncLogger, we’ll stick with that for consistency:

XML Configuration (log4j2.xml)

<!-- Keep your desired Mule HTTP message debug logs -->
<AsyncLogger name="org.mule.module.http.internal.HttpMessageLogger" level="DEBUG"/>

<!-- Suppress all AWS SDK debug logs entirely -->
<AsyncLogger name="com.amazonaws" level="INFO"/>

<!-- If you want granular control (only block specific noisy AWS loggers), use these instead: -->
<!-- <AsyncLogger name="com.amazonaws.shade.request" level="INFO"/> -->
<!-- <AsyncLogger name="com.amazonaws.shade.requestId" level="INFO"/> -->
<!-- <AsyncLogger name="com.amazonaws.shade.auth.AWS4Signer" level="INFO"/> -->

Properties Configuration (log4j2.properties)

If you’re using the properties format instead, here’s the equivalent:

# Preserve Mule HTTP debug logs
logger.mule-http.name = org.mule.module.http.internal.HttpMessageLogger
logger.mule-http.level = DEBUG
logger.mule-http.additivity = false

# Turn off AWS debug logs
logger.aws.name = com.amazonaws
logger.aws.level = INFO
logger.aws.additivity = false

# Granular alternative for specific noisy AWS loggers:
# logger.aws-request.name = com.amazonaws.shade.request
# logger.aws-request.level = INFO
# logger.aws-request.additivity = false

Why this works: #

The AWS logs you’re seeing come from the AWS SDK’s internal logging system, which uses the com.amazonaws (and nested com.amazonaws.shade.*) logger namespaces. By setting their level to INFO, you’ll still get important AWS-related info/warn/error logs, but the verbose debug logs (like request sending/receiving details) will be suppressed. Your Mule HTTP message logs live in a separate namespace (org.mule.module.http.internal.HttpMessageLogger), so they’ll keep running at DEBUG level as intended.

Give this a try—your log files should be back to showing only the HTTP logs you care about, without the AWS noise!

内容的提问来源于stack exchange，提问作者ViS