Logging and Debugging
|
Standard Support for Mule 4.1 ended on November 2, 2020, and this version of Mule reached its End of Life on November 2, 2022, when Extended Support ended. Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted. MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements. |
MuleSoft provides a variety of logging and debugging options for Mule apps.
Application logs and a runtime log help you monitor and troubleshoot your apps and the Mule server. For details, see Configuring Logging.
You can enable verbose logging for connectors and modules to record debug level information in the logs.
The Logger component can help you monitor or even debug your Mule app by logging important information such as error messages, status notifications, payloads, and so on. You can add a Logger anywhere in a flow, and you can configure it to log a string that you specify, the output of a DataWeave expression you write, or any combination of strings and expressions. For details, see Logger Component in the Core component documentation.
To control the display of Mule stack traces, you can use command-line arguments or set properties in Anypoint Studio. For details, see Configuring Mule Stack Traces.
To troubleshoot a Mule app in Anypoint Studio, you can use the Studio Visual Debugger, which lets you set breakpoints to stop execution and check events. If you are creating your Mule app outside of Studio, you can either use MUnit to test your app, or you can activate remote debugging. For details, see Debugging Outside Studio.