---
schema_version: "1"
id: 69b782e606d3e23d96fcb4b1beba57bc6a077296c75706b5aeb3a43c4a1edf96
title: Business Events
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.6/business-events.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.6/business-events
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 0094f8232d34a1fa5f683fe6d16d5551aa9c21bfacf61322a368eb775b9daf4c
description: MuleSoft Documentation Site
release: "4.6"
latest: false
---
---
product: Mule Runtime
version: 4.6
---

# Business Events

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

Mule applications collect _business event_ information (such as transaction execution time, errors,
success or failure results, and message payload information) about flows and message processors that
handle your _business transactions_:

- Events map to message processors and connectors and are the low-level details of a transaction.
  Events are not supported in batch processing.

- Transactions are logical groupings of related events that often correspond to a business view of
  the system, at the flow level.

## Business Event Types

You can track two types of business events: _default events_ and _custom events_.

Default event tracking is supported by all connectors and selected message processors. Enabling
default events for these elements enables you to perform advanced debugging at runtime. You can
enable default event tracking at either the flow level or the message processor level.  
See [Configure Default Events Tracking](https://docs.mulesoft.com/mule-runtime/4.6/business-events-in-components) for configuration details.

Custom event tracking is supported by the Custom Business Event component. Custom events are always
tracked, enabling you to monitor high-level activities in your flow that are relevant to your
business.  
See [Custom Business Event Component](https://docs.mulesoft.com/mule-runtime/4.6/business-events-custom) for configuration details.

## Monitoring Business Events

You can enable Insight in Runtime Manager to monitor business events at runtime. These events can
help you analyze the root cause of failures, isolate performance bottlenecks, and test for
compliance with company procedures.

Certain default events are tracked automatically after you enable Insight, but you must enable
others in your application before they are tracked.

See the [Insight](https://docs.mulesoft.com/runtime-manager/insight) documentation for more details.

## Best Practices for Business Events

Consider the following recommended practices when configuring business events tracking:

- Enable default events only for processes that have particular value to you. To filter out
  unnecessary information, determine which stages within a business transaction you need to track,
  and enable tracking for only those stages.

- Use custom events to track key process indicators: for example, "Total Order Amount" or "Tracking
  Number" to surface the high-level business activities in your flow.

- Customize the transaction ID so that meaningful information, such as an order number, an employee
  identification number, or a shipment tracking number, is displayed for a transaction.  
  This practice makes analysis and debugging easier and more intuitive at runtime.

## See Also

- [Mule Events](https://docs.mulesoft.com/mule-runtime/4.6/about-mule-event)

- [Transaction Management](https://docs.mulesoft.com/mule-runtime/4.6/transaction-management)

- [Configure Default Events Tracking](https://docs.mulesoft.com/mule-runtime/4.6/business-events-in-components)

- [Custom Business Event Component](https://docs.mulesoft.com/mule-runtime/4.6/business-events-custom)