How can you trace messages in MuleSoft?

How can you trace messages in MuleSoft?

• A. Correlation IDs must be added manually to each log line.
• B. The correlation id is automatically logged on cloudhub and customer-hosted runtimes.
• C. Correlation id is not logged by default.
• D. Correlation id is logged only for DEBUG level messages.

Answer: (B)

Tracing messages with a correlation id travels alongside the request as it moves through flows and external calls, enabling end-to-end visibility. On CloudHub and customer-hosted runtimes, this correlation id is automatically included in log entries, so you don’t have to add it manually or enable special logging. This automatic logging makes it easy to search for a single request across systems and reconstruct its path. It’s not correct that the id isn’t logged by default or that you must log only at DEBUG level—the runtime handles it for you as part of normal logging on supported environments.

Tracing messages with a correlation id travels alongside the request as it moves through flows and external calls, enabling end-to-end visibility. On CloudHub and customer-hosted runtimes, this correlation id is automatically included in log entries, so you don’t have to add it manually or enable special logging. This automatic logging makes it easy to search for a single request across systems and reconstruct its path. It’s not correct that the id isn’t logged by default or that you must log only at DEBUG level—the runtime handles it for you as part of normal logging on supported environments.