---
schema_version: "1"
id: 060f948c89dd0f79cdd43b803c72f0f26c62a537b18dc869b130b34a486210b8
title: Configure Default Events Tracking
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.3/business-events-in-components.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.3/business-events-in-components
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 411f2d051a590a168ceff516c44c490e6d2a3a9a6275bebbf9440b8037eae271
description: MuleSoft Documentation Site
release: "4.3"
latest: false
---
---
product: Mule Runtime
version: 4.3
---

# Configure Default Events Tracking

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

Because event tracking requires processing and network overhead to aggregate and store the events
that Mule runtime engine generates, it is disabled by default. However, you can enable and configure
default events tracking for connectors or message processors that support it, at one of two levels:

- At the flow level

- At the message processor (connector or component) level, which takes precedence over the flow
  level setting

After you enable event tracking, customize the transaction ID to identify specific tracked events so
that you can analyze them at runtime.

## Flow-Level Event Tracking

Use this option to enable default event tracking for all elements in a flow that support event
tracking. You can disable tracking for specific processors or connectors to override the flow level
setting.

Steps to enable default events tracking for all components in a flow:

1.  Select your flow component to open the properties view.

2.  Enable default business events using either the UI or XML:

    - In the UI, select **Enable default events tracking**:

      ![default-event-tracking-flow](/mulesoft/current/en-us/mule-runtime/4.3/_images/mruntime-business-event-flow.png)

    - In the XML, add attribute `tracking:enable-default-events="true"` to the `flow` element:

      ```xml
      <flow name="testFlow" tracking:enable-default-events="true">
      ```

3.  Save your settings.

## Message Processor-Level Event Tracking

You can enable event tracking on individual connectors and components that support event tracking.

Steps to enable enable default events tracking for an individual component:

1.  Open the connector or component properties view.

2.  Enable default business events using any of the following options:

    - In the UI, select **Enable default events tracking**:

      ![default-event-tracking-component](/mulesoft/current/en-us/mule-runtime/4.3/_images/mruntime-business-event-component.png)

    - In the XML, add attribute `tracking:enable-default-events="true"` inside your component
      element:

      ```xml
      <flow name="flow">
        ...
          <choice doc:name="Choice" tracking:enable-default-events="true"/>
        ...
      </flow>
      ```

3.  Save your settings.

## Customize the Transaction ID

The Set Transaction Id component enables you to set an identifier for all tracked events so that
meaningful information, such as an order number, is displayed for a transaction when analyzing
tracked events at runtime, whether using Anypoint Runtime Manager or CloudHub.

The transaction ID supports DataWeave expressions, which enables you to create an ID dynamically and
include information related to the event into the ID.

Follow these steps to set a transaction ID either in Anypoint Studio or by editing the configuration
XML:

- In the Studio UI:

  1.  Drag the **Set Transaction Id** component to your flow.

  2.  In the **Set Transaction ID** configuration screen, set an ID value for the **Transaction ID**
      field:

      ![custom-transaction-id](/mulesoft/current/en-us/mule-runtime/4.3/_images/mruntime-custom-transaction-id.png)

- In the XML editor:

  - Add a child element to the `flow` element:

    ```xml
    <flow name="flow">
    ...
      <tracking:transaction id="#[payload.orderId]" />
    ...
    </flow>
    ```

## See Also

[Business Events](https://docs.mulesoft.com/mule-runtime/4.3/business-events)