When a Mule Runtime or an application loses sync with Anypoint API Manager, changes to online policies will not reflect and analytics will not be sent.
This article describes the Log4j loggers that should be enabled for troubleshooting communication issues between the API Manager client and the Anypoint platform.
For Standalone Mule Runtime
Enable the following loggers in MULE_HOME/conf/log4j2.xml:
<Loggers>
...
<AsyncLogger name="com.mulesoft.module.client" level="TRACE" />
<AsyncLogger name="com.mulesoft.module.policies" level="DEBUG" />
<AsyncLogger name="com.mulesoft.analytics" level="DEBUG" />
<AsyncLogger name="org.mule.module.http.internal.HttpMessageLogger" level="DEBUG" />
<AsyncLogger name="com.ning.http" level="DEBUG" />
...
</Loggers>
<Loggers>
...
<AsyncLogger name="com.mulesoft.mule.runtime.gw.analytics" level="TRACE"/>
<AsyncLogger name="com.mulesoft.mule.runtime.gw" level="DEBUG" />
<AsyncLogger name="com.mulesoft.extension.policies" level="DEBUG"/>
<AsyncLogger name="com.mulesoft.mule.runtime.gw.client" level="TRACE"/>
...
</Loggers>
For Runtime Fabric
Per the Runtime Fabric document Log Levels, you can use the Anypoint Runtime Manager to change the application log level by configuring the following property:
1. Mule 3
logging.level.com.mulesoft.module.client=TRACE logging.level.com.mulesoft.module.policies=DEBUG logging.level.com.mulesoft.analytics=DEBUG logging.level.org.mule.module.http.internal.HttpMessageLogger=DEBUG logging.level.com.ning.http=DEBUG
2. Mule 4
logging.level.com.mulesoft.mule.runtime.gw.analytics=TRACE logging.level.com.mulesoft.mule.runtime.gw=DEBUG logging.level.com.mulesoft.extension.policies=DEBUG logging.level.com.mulesoft.mule.runtime.gw.client=TRACE
For a CloudHub application
You need to add the following configurations to the Settings page of the application in Runtime Manager -> Logging tab:
TRACE com.mulesoft.module.client TRACE com.mulesoft.module.policies TRACE com.mulesoft.analytics TRACE org.mule.module.http.internal.HttpMessageLogger TRACE com.ning.http
2. Mule 4
TRACE com.mulesoft.mule.runtime.gw.analytics TRACE com.mulesoft.mule.runtime.gw TRACE com.mulesoft.extension.policies
After configuring the logger levels, resulting logging will be found in the application log files.
To trace a request as it passes through the different policies applied to a Mule Application, refer to the following link:
001114857

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.