- 2 minutes to read

Mule ESB Logging Overview

Nodinite empowers you to achieve robust, business-driven logging from Mule ESB and MuleSoft (Anypoint) flows. Choose the approach that best fits your integration landscape and unlock powerful monitoring, troubleshooting, and analytics.

  1. Mule ESB - Custom Connector – This is the recommended option. By using the Nodinite Pickup Log Events Service Logging Agent, you eliminate the need for the Mule ESB Logging Agent and gain a future-proof, scalable solution.
  2. Built-in logging shapes – NOT recommended for most scenarios, but still supported:

The Mule ESB Logging Agent leverages the output from the Log4J framework (option 2) to retrieve context and message body from Mule ESB flows running on-premise or in the cloud. Learn how to configure Log4J here.

You write the required logging code directly within your Mule Flows, giving you full control and flexibility.

Important

Set Message Type for searchable business data - When logging from Mule ESB flows, the Message Types field (using OriginalMessageTypeName or im_messageType) determines which Search Field Expressions extract business data like Order Numbers, Customer IDs, and Invoice amounts. Without proper Message Types, features like Non-Events Monitoring, Business Process Modeling (BPM), and business-data searches in Log Views won't function. Configure Message Types in your Mule flow logging code before deploying to production.

To correlate messages within Mule Flows, configure a session variable. See the 'How do I correlate logged events?' user guide for best practices.

Next Step

Message Types - Critical for Search Field extraction from Mule ESB events
Search Field Expressions - Extract business data from flow messages
Log Views - Search logged data by business identifiers
Non-Events Monitoring - Track message volumes and patterns
Business Process Modeling (BPM) - End-to-end transaction correlation
Log Agents