---
schema_version: "1"
id: 4c83bbcdb71f9ca67287bb736b2b98c88fa4f02524d7934ff2c5ef78598abf0f
title: Configuring Distributed Tracing for Managed Omni Gateway
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/latest/managed-tracing-config.md
canonical_url: https://docs.mulesoft.com/gateway/latest/managed-tracing-config
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 5125fb037c6b189488e4647511a43a2c7714f2b722b7e0ee2b3ff4e11b81c5ca
description: MuleSoft Documentation Site
release: "1.14"
latest: true
---
---
product: Omni Gateway
version: 1.14
is-latest-version: true
---

# Configuring Distributed Tracing for Managed Omni Gateway

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

OpenTelemetry provides a unified standard for instrumenting, generating, collecting, and exporting
telemetry data across distributed systems. Omni Gateway supports OpenTelemetry, enabling you to
configure the generation of distributed tracing data for all API traffic managed by the gateway.
This integration delivers deep visibility into API request flows, making it easier to analyze system
behavior, troubleshoot issues, and understand interactions between Omni Gateway APIs and external
services.

Tracing enables you to track Omni Gateway API interactions. When multiple systems and services are
involved, distributed tracing tracks API requests as they flow through distributed environments,
providing a comprehensive view of the API’s execution.

With the Anypoint Monitoring Telemetry Exporter, you can send Omni Gateway trace data to third-party
observability and analytics platforms, including Azure Monitor, Splunk HEC, or any
OpenTelemetry-compliant tool. This capability allows you to leverage end-to-end observability,
correlating API traces with data from other systems to build a comprehensive view of your
environment.

Configure distributed tracing for Managed Omni Gateway using one of these methods:

- [Managed Omni Gateway deployment](#managed-deployment-config): Set initial distributed tracing
  values when you create the gateway.

- [Runtime Manager runtime configurations](#runtime-manager-config): Applies to all API instances in
  the gateway after the gateway is deployed.

- [Policy](#policy-config): Applies to one API instance and provides granular control.

## Configuration Precedence

When you configure a setting in more than one place, Omni Gateway uses the first value that is set,
in this order of precedence:

1.  **Policy**: A policy applied to the API instance.

2.  **Runtime Manager runtime configuration**: Used if no policy value is set.

3.  **Built-in default**: Used if neither of the other values is set. A policy value overrides the
    gateway-level value for the API instance it’s applied to. API instances without the policy use
    the gateway-level value.

## Before You Begin

To use the OpenTelemetry with Omni Gateway, you must be familiar with:

- Distributed tracing concepts, including traces and spans.

  If you’re new to distributed tracing and OpenTelemetry, we recommend starting with
  [What is OpenTelemetry](https://opentelemetry.io/docs/concepts/what-is-opentelemetry/) and
  [Understanding distributed tracing](https://opentelemetry.io/docs/concepts/observability-primer/#understanding-distributed-tracing).

## Configure Distributed Tracing During Managed Gateway Deployment

Set distributed tracing values in the deployment flow when you create a Managed Omni Gateway. For
the UI steps and parameter descriptions, see
[Deploy a Managed Omni Gateway](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up).

## Configuring Omni Gateway Distributed Tracing in Runtime Manager

1.  In Anypoint Platform, select **Runtime Manager**.

2.  Select **Omni Gateways**.

3.  Select your Omni Gateway.

4.  Open **Runtime Configurations**.

5.  Open **Distributed Tracing**.

6.  Enable **Distributed tracing**.

7.  Set the **Sampling percentage** to the percentage of transactions to trace.

    To configure sampling only on a per-API basis with the Tracing policy, set **Sampling
    percentage** to `0`.

8.  Apply the changes.

> [!NOTE] The **Sampling percentage** corresponds to the `overall` sampling percentage. The `client`
> and `random` sampling percentages default to `100` when **Sampling percentage** is set to a
> non-zero value.

## Configure Distributed Tracing for Specific APIs

To override the globally configured distributed tracing settings for specific APIs, apply the
Tracing policy. First enable and configure distributed tracing for the gateway, then apply this
policy to the APIs to instrument:

- [Tracing Policy](https://docs.mulesoft.com/gateway/latest/policies-included-tracing)

## Export Traces from Anypoint Monitoring to Third Parties

To export traces to third-party providers using the Anypoint Monitoring Telemetry Exporter, see
[Exporting Telemetry Data to Third-Party Monitoring Systems](https://docs.mulesoft.com/monitoring/telemetry-exporter).