---
schema_version: "1"
id: e945d9847f288f53486838cb534900bdecfb01380032ff19529d830a08ce2d85
title: Examining Traces
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/monitoring/traces.md
canonical_url: https://docs.mulesoft.com/monitoring/traces
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 0f42d3aa0f65f473420c7e7c8ea879fd126e3a5f7bfc7f47646f55dcdf4bcc0e
description: Use Traces in MuleSoft Anypoint Monitoring to track the flow of requests through service pipelines, troubleshoot errors, and optimize performance using OpenTelemetry span data.
latest: true
---
---
product: Monitoring
description: Use Traces in MuleSoft Anypoint Monitoring to track the flow of requests through service pipelines, troubleshoot errors, and optimize performance using OpenTelemetry span data.
keywords: MuleSoft, Anypoint Monitoring, traces, distributed tracing, OpenTelemetry, OTEL, service pipelines, request tracing, span data, troubleshooting
---

# Examining Traces

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

[![](/mulesoft/current/en-us/_/img/icons/info.svg)](/monitoring/#billing)

On US and EU Cloud instances of Anypoint Platform, use Traces in Anypoint Monitoring to track the
flow of requests that travel through service pipelines. Get data from the Open Telemetry (OTEL)
spans that form your traces. Troubleshoot requests with errors or slow response times, optimize your
resource allocation, and track calls end-to-end. Monitor the performance of a specific transaction
as it travels through services.

![Span list in Traces Overview](/mulesoft/current/en-us/monitoring/_images/traces.png)

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>Traces in Anypoint Monitoring</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td><a href="#environments">Environment selector</a> for your deployments (such as Sandbox or Production)</td></tr><tr><td><i data-value="3"></i><b>3</b></td><td><a href="#filters">Filter</a> field for queries that narrow the list of logs to return</td></tr><tr><td><i data-value="4"></i><b>4</b></td><td>List of spans for the supported agents, brokers, MCP servers, and Mule apps</td></tr><tr><td><i data-value="5"></i><b>5</b></td><td>Lookback selector for the period of time to capture in the <strong>Span List</strong> (from the default of 15 minutes to the last seven days)</td></tr><tr><td><i data-value="6"></i><b>6</b></td><td>Auto-Refresh every 5, 15, or 30 minutes, every hour, or one time per day</td></tr><tr><td><i data-value="7"></i><b>7</b></td><td>Manual refresh button</td></tr></tbody></table>

In addition to reviewing traces in Anypoint Monitoring, you can use
[Telemetry Exporter](https://docs.mulesoft.com/monitoring/telemetry-exporter) to export traces to third-party observability and analytics
platforms.

## Traces Availability

Traces are available for specific:

- [Spans](#support-spans)

- [Hosts](#support-hosts)

- [Sampling Rates](#support-sampling)

### Supported Traces

Traces include spans for:

- Agentic assets: Agents, brokers, and MCP servers

- Flows: Mule flows for the selected task of the specific service

- Events: Mule runtime events or user actions for the selected service

### Hosts

Traces in Anypoint Monitoring displays spans from entities deployed to:

- CloudHub 2.0

- Anypoint Runtime Fabric (Limited Availabilty)

### Sampling Rate

Trace data sampling rate:

- 100%: Agents, brokers, and MCP servers

- 10%: Mule apps and APIs

## Before You Begin

For all types of traces, these prerequisites apply:

- The Anypoint Integration Advanced package or a Titanium subscription to Anypoint Platform

- [Permission to view](https://docs.mulesoft.com/access-management/permissions-by-product#monitoring) Mule apps, APIs, and
  agentic assets (agent, broker, and MCP server instances) in Anypoint Monitoring

For Mule app and API tracing, these prerequisites apply:

- For apps deployed to CloudHub 2.0:

  - [Enable trace data collection for your app in a shared space](https://docs.mulesoft.com/cloudhub-2/ch2-deploy-shared-space#enable-trace-data-collection)

  - [Enabled trace data collection for your app in a private space](https://docs.mulesoft.com/cloudhub-2/ch2-deploy-private-space#enable-trace-data-collection)

- For Runtime Fabric, enabled trace data collection on apps deployed to
  [Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/use-anypoint-monitoring#enable-trace-data)

- Mule runtime version 4.6 or later

- HTTP Connector version 1.8 or later

## Get Traces from Traces Overview

View a list of spans from across entities (agents, brokers, MCP servers, and Mule apps) in **Traces
Overview** in Anypoint Monitoring. Get high-level details on each root span in a trace. Use filters
to narrow the scope of spans in the **Spans List**. Get additional detail on each span in the
hierarchy of spans that form a trace (from root span to its descendants).

1.  Log in to Anypoint Platform with a user account that has
    [permission to access Anypoint Monitoring content](https://docs.mulesoft.com/monitoring/am-permissions).

2.  Navigate to Anypoint Monitoring:

    Click **Monitoring** from the Anypoint Platform home page or from the **Runtimes** menu in the
    header.

3.  In the sidebar, click **Traces**.

4.  Make sure you’re using the [business group](#business-groups) that contains the spans.

5.  Select up to the last seven days of spans (see [item 5](#traces-overview)).

    15 minutes is the default.

6.  Select the [environment](#environments) that contains your spans.

7.  Optionally, provide a [filter query](#filters) to narrow the search results.

8.  [Get trace details](#get-trace-details).

## Find Traces for Agent Visualizer Nodes

Agent Visualizer links to traces for agentic assets (agent, broker, and MCP server instances).

1.  In Agent Visualizer, click a node to open its detail card.

2.  Click **View Traces** to navigate to the traces for the node in **Trace Details** (in Anypoint
    Monitoring).

3.  [Get trace details](#get-trace-details).

For more information about nodes in Agent Visualizer, see
[Agent Visualizer Overview](https://docs.mulesoft.com/agent-visualizer/).

## Get Trace Details

After navigating to **Trace Details** from [**Traces Overview**](#trace-overview) in Anypoint
Monitoring or from a [node in Agent Visualizer](#visualizer), get information about the trace and
its spans.

1.  Review information about the trace:

    **Trace Details** displays the selected instance’s traces in a span tree, starting from the root
    span for the instance.

    ![An instance’s spans in the Traces Details page](/mulesoft/current/en-us/monitoring/_images/trace-details.png)

    1.  **Trace Details** page for a span selected from **Trace Overview** or through a node in
        Agent Visualizer

    2.  High-level data about the selected span:

        - **Status Code**: HTTP response status of the trace (for example, `0 No Response`,
          `200 OK`,`500 Internal Server Error`)

        - **Span Start Time**: The time the trace started, in UTC

        - **Total Response Time**: The time taken for the trace to execute

        - **Root Span**: The request or operation that initiated the trace

    3.  Search for spans by full or partial matches to the span name

        The page displays matching spans.

    4.  Trace hierarchy of spans, starting from the root span through its descendants

    5.  Trace ID of the root span

2.  To get more information about a span in the details page, click the span:

    ![Details of a span in the Traces Details page](/mulesoft/current/en-us/monitoring/_images/trace-details-span.png)

    1.  **Span Name**: Name of the span.

    2.  [Span details](#span-details)

## Filter Spans

To narrow the list of spans in **Traces Overview**, provide a filter query in the search field.

1.  Place your cursor within the search field and click to display a list of filters.

2.  Select a filter from the field’s dropdown.

    <table id="filter-list"><colgroup><col> <col> <col></colgroup><thead><tr><th>Filter</th><th>Operators</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p><code>api_instance_id</code></p></div></div></td><td><div><div><p><code>=</code></p></div></div></td><td><div><div><p>Version of an API instance that’s associated with a span. You can find the instance’s ID in API Manager.</p></div></div></td></tr><tr><td><div><div><p><code>correlation_id</code></p></div></div></td><td><div><div><p><code>=</code></p></div></div></td><td><div><div><p>Correlation ID associated with a span (see <a href="https://docs.mulesoft.com/mule-runtime/latest/correlation-id">Correlation ID</a>).</p></div></div></td></tr><tr><td><div><div><p><code>entity_name</code></p></div></div></td><td><div><div><p><code>=</code>, <code>IN</code></p></div></div></td><td><div><div><p>Name of entities associated with spans.</p></div></div></td></tr><tr><td><div><div><p><code>http_status_code</code></p></div></div></td><td><div><div><p><code>=</code>, <code>IN</code></p></div></div></td><td><div><div><p>HTTP status codes associated with span.</p></div></div></td></tr><tr><td><div><div><p><code>span_id</code></p></div></div></td><td><div><div><p><code>=</code></p></div></div></td><td><div><div><p>ID of a span contained in traces.</p></div></div></td></tr><tr><td><div><div><p><code>span_name</code></p></div></div></td><td><div><div><p><code>=</code>, <code>IN</code></p></div></div></td><td><div><div><p>Name of a span.</p></div></div></td></tr><tr><td><div><div><p><code>trace_id</code></p></div></div></td><td><div><div><p><code>=</code>, <code>IN</code></p></div></div></td><td><div><div><p>ID associated with a span.</p></div></div></td></tr></tbody></table>

3.  Select an operator for the filter:

    - `=` accepts a single alphanumeric value.

    - `IN` accepts one or more comma-separated, alphanumeric values. The values get processed as
      logical ORs.

4.  Select a value from the search field’s **Top Value** list. If the value you’re looking for isn’t
    in the list, start typing a partial match to your value, and then select the value.

    Tip: If you’re providing search values to the `IN` operator (such as
    `entity_name IN ['value1', 'value2']`), manually adding a comma after a value before selecting
    another value from the **Top Value** list can help with valid query formation.

    Example:

    This example gets spans named `my-span` that have status code '404', '502', or '200':

    `http_status_code IN [ '404', '502', '200' ] span_name = my-span`

To edit or delete a filter, click the filter, and then click **Edit Filter** or **Delete Filter**
from the **Actions** list for the filter. To avoid issues when editing, you can delete the filter
and then add it back with the values you want.

Tips:

- If no traces appear after applying a query, change your filters, the lookback setting, or business
  group.

- Selecting multiple filters of the same type isn’t allowed.

- Filters get processed as logical ANDs. If a span doesn’t match one of the filters, the query won’t
  return spans.

## Span Details

Traces provide information about a root span and its descendants in dedicated **Trace Details**
pages. Each span listed on the page links to details about that span:

- **Span Duration**: Time the span took to execute

- **Span Status**: Status of the span (**OK**, **ERROR**, **Unset**)

- **Span ID**: ID of the span

- **Span Kind**: Source of the span operation or request (**Server**, **Internal**, **Client**)

- **Span Start Time**: Time that the span started, in UTC

- **Trace ID**: ID of the trace in which the span occurred

- **Correlation ID**: Unique identifier that’s generated before sending an event to the next
  processor in the Mule flow (see [Correlation ID](https://docs.mulesoft.com/mule-runtime/latest/correlation-id))

- **HTTP Status Code**: HTTP status code of a span that is a request. Statuses include **0 No
  Response**, **200 OK**, and **500 Internal Server Error**.

- **Entity Type**: Type of entity associated with the trace. Types include **App**, **API**.

- **Entity Name**: Name of the entity associated with the trace

- [**Business Group**](#business-groups) that the span belongs to

- [**Environment**](#environments) that the span belongs to

- **Parent Span ID**: ID of a span that contains the selected span

  Parent spans don’t have a value in this field. Use the Trace ID to track this span.

- **View Logs**: Find the root span in Anypoint Monitoring logs.

## Environments

Select the environment containing the spans you want to review in **Traces Overview**.

Your organization administrator
[creates](https://docs.mulesoft.com/access-management/environments#to-create-a-new-environment) the environments that are
available to you.

Anypoint Platform supports these _types_ of
[environments](https://docs.mulesoft.com/access-management/environments#types-of-environments.adoc):

- **Design**

- **Production**

- **Sandbox**

## Business Groups

If you work from the root organization level, you can query all spans across the entire
organization. If you’re working from a business group that’s a descendant of the root, the query
returns spans from that business group only.

To view or select a different business group, use the business group dropdown.

![Business group menu](/mulesoft/current/en-us/monitoring/_images/business-groups.png)

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>Business group that contains spans in the <strong>Span List</strong></td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>Selectable business groups<div><p>In the example, the root organization is active.</p></div></td></tr></tbody></table>

## See Also

- [Exporting Telemetry Data to Third-Party Monitoring Systems](https://docs.mulesoft.com/monitoring/telemetry-exporter)

- [Enable Trace Data Collection](https://docs.mulesoft.com/cloudhub-2/ch2-deploy-shared-space#enable-trace-data-collection)
  (Shared Space)

- [Enable Trace Data Collection](https://docs.mulesoft.com/cloudhub-2/ch2-deploy-private-space#enable-trace-data-collection)
  (Private Space)