---
schema_version: "1"
id: 90e550c298411af8bf612e1f9ff65568dc5332c4f6658205ca3f9a99c7af5246
title: Logging and Debugging
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.9/logging-and-debugging.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.9/logging-and-debugging
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 2b691c2ed38ff7293cfcd2f6f569e0135d55d75395f963376da79de3969d133f
description: MuleSoft Documentation Site
release: "4.9"
latest: false
---
---
product: Mule Runtime
version: 4.9
---

# Logging and Debugging

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

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](https://docs.mulesoft.com/mule-runtime/4.9/logging-in-mule).

You can [enable verbose logging](https://docs.mulesoft.com/mule-runtime/4.9/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](https://docs.mulesoft.com/mule-runtime/4.9/logger-component-reference) 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](https://docs.mulesoft.com/mule-runtime/4.9/configuring-mule-stacktraces).

To troubleshoot a Mule app in Anypoint Studio, you can use the
[Studio Visual Debugger](https://docs.mulesoft.com/studio/visual-debugger-concept), 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](https://docs.mulesoft.com/mule-runtime/4.9/debugging-outside-studio).

If you are running your Mule application in CloudHub, see
[View Log Data](https://docs.mulesoft.com/cloudhub/viewing-log-data) for additional information about log data and
persistence.