---
schema_version: "1"
id: b2b219cc0503444cf23dc9a0bd7d2e033664c8d5539154ad91c55c7a23fd2474
title: Using Anypoint Monitoring with Runtime Fabric
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-fabric/latest/use-anypoint-monitoring.md
canonical_url: https://docs.mulesoft.com/runtime-fabric/latest/use-anypoint-monitoring
source_site: docs.mulesoft.com
content_type: documentation
content_hash: bb278fb16afa15f8d7091707319c20183ab4519b33f2b35f214b4da463b82460
description: MuleSoft Documentation Site
release: "3.0"
latest: true
---
---
product: Runtime Fabric
version: 3.0
is-latest-version: true
---

# Using Anypoint Monitoring with Runtime Fabric

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

Anypoint Runtime Fabric includes native support for [Anypoint Monitoring](https://docs.mulesoft.com/monitoring/), which
collects and exposes metrics, logs, and traces for Mule apps and API gateways deployed to Runtime
Fabric.

Metrics collection is enabled by default for all plans. Log and trace collection require an
[Anypoint Platform Integration Advanced](https://www.mulesoft.com/anypoint-pricing) subscription.

## Before You Begin

### Verify Network Connectivity

For metrics, logs, and traces to reach Anypoint Monitoring, each node in Runtime Fabric must be able
to send outbound traffic to the control plane ingestion endpoint for your region.

For Runtime Fabric agent version 2.6.22 and later, the monitoring sidecar sends HTTPS traffic on TCP
port 443 to these domains:

- US Cloud: `us1.ingest.mulesoft.com`

- EU Cloud: `eu1.ingest.mulesoft.com`

- Canada Cloud (port 8443, OTEL): `ingest.ca1.platform.mulesoft.com`

- Japan Cloud (port 8443, OTEL): `ingest.jp1.platform.mulesoft.com`

- India Cloud (port 8443, OTEL): `ingest.in1.platform.mulesoft.com`

- Australia Cloud (port 8443, OTEL): `ingest.au1.platform.mulesoft.com`

- United Kingdom Cloud (port 8443, OTEL): `ingest.gb1.platform.mulesoft.com`

> [!NOTE] For Runtime Fabric versions earlier than 2.6.22, the agent sends TCP (Lumberjack) traffic
> on port 443 to a different domain. After you upgrade to 2.6.22 or later and redeploy all
> applications, these domains are no longer used:
>
> - US Cloud: `dias-ingestor-router.us-east-1.prod.cloudhub.io`
>
> - EU Cloud: `dias-ingestor-router.eu-central-1.prod-eu.msap.io`
>
> For Runtime Fabric versions earlier than 1.8.50, use port 5044 (TCP Lumberjack) and these domains:
>
> - US Cloud: `dias-ingestor-nginx.prod.cloudhub.io`
>
> - EU Cloud: `dias-ingestor-nginx.prod-eu.msap.io`

For the full list of required endpoints, see
[Configure Network for Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/install-self-managed-network-configuration).

If your cluster uses an outbound proxy, configure Runtime Fabric to route monitoring traffic through
it. See [Configure Proxies on Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/manage-proxy-self).

> [!NOTE] Starting with Runtime Fabric agent version 2.6.22, the Anypoint Monitoring sidecar
> supports HTTP proxy only. SOCKS5 proxy is not supported for monitoring traffic.

### Review Subscription Requirements

<table><colgroup><col> <col></colgroup><thead><tr><th>Feature</th><th>Subscription required</th></tr></thead><tbody><tr><td><p>Metrics</p></td><td><p>All plans</p></td></tr><tr><td><p>Logs</p></td><td><p><a href="https://www.mulesoft.com/anypoint-pricing">Anypoint Platform Integration Advanced</a></p></td></tr><tr><td><p>Traces</p></td><td><p><a href="https://www.mulesoft.com/anypoint-pricing">Anypoint Platform Integration Advanced</a></p></td></tr></tbody></table>

## Collect Metrics

Metrics collection is automatic. When a Mule app or API gateway replica is deployed to Runtime
Fabric, a monitoring sidecar is deployed alongside it and begins transmitting metrics data to
Anypoint Monitoring via mutual TLS encryption.

Each replica caches up to 100 MB of metrics data. If the connection to Anypoint Monitoring is
interrupted, the cache typically provides at least four days of storage per replica before data is
rotated. Custom metrics may consume cache faster.

These Runtime Fabric operations do not affect or restore existing metrics data:

- Backup and restore

- Runtime Fabric upgrade

- OS patching of nodes

## Enable and Configure Log Forwarding

Log forwarding requires an
[Anypoint Platform Integration Advanced](https://www.mulesoft.com/anypoint-pricing) subscription.
When enabled, Anypoint Monitoring provides access to [log data](https://docs.mulesoft.com/monitoring/logs) for
applications deployed to Runtime Fabric.

To enable log forwarding for a Mule app:

1.  In Runtime Manager, open the application and click the **Logging** tab.

2.  Select the **Enable application logs** option.

3.  Select the log level from the drop-down list:

    - **INFO**: Informative messages

    - **DEBUG**: Debugging messages

    - **WARNING**: Warning messages

    - **ERROR**: Error messages, such as when an exception occurs

    - **FATAL**: Fatal messages for when an application fails

4.  Optionally, set the log level for a specific Java package class by selecting the log level,
    entering the `package.name`, and pressing the Enter key.

5.  Click **Apply Changes**.

### Log Storage and Throughput

Each replica stores up to 450 MB of log data on disk. When the limit is reached, older log data is
rotated to make room for new entries.

The log forwarding sidecar can transmit up to 300 KB of log data per second per replica.

In some cases, multi-line log entries may not be fully transmitted. This can occur when multiple
lines are split across two files during log rotation inside Runtime Fabric.

### Log Forwarding Architecture

Starting with Runtime Fabric agent version 3.0.0, logs are forwarded exclusively through a sidecar
container deployed alongside each application replica. This replaces the previous DaemonSet-based
approach and provides better isolation and resource management.

> [!NOTE] If you are upgrading from Runtime Fabric agent version 2.11.x or earlier, you must
> complete migration steps before upgrading to version 3.0.0. See
> [Migrate Log Forwarding Before Upgrading Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/migrate-log-forwarding).

## Enable Trace Data Collection

> [!NOTE] This feature is available only if your organization has the Anypoint Integration Advanced
> package or a Titanium subscription to Anypoint Platform. For more information, see the
> [Pricing and Packaging](https://docs.mulesoft.com/general/pricing) documentation.

Traces provide full visibility into the execution path of API calls and application transactions.
When enabled, Anypoint Platform collects tracing information from Mule runtime engine in the
OpenTelemetry standard, which you can export using the Anypoint Monitoring
[Telemetry Exporter](https://docs.mulesoft.com/monitoring/telemetry-exporter).

### Prerequisites for Traces

- Mule runtime version 4.6 or later

- Runtime Fabric agent version 2.6.31 or later

- Traces can only be enabled using the Runtime Manager UI or API. The Mule Maven plugin, Anypoint
  CLI, and Anypoint Studio are not supported.

### Enable Tracing for an App

1.  In Runtime Manager, open the application.

2.  Click the **Monitoring** tab.

3.  Select the **Enable tracing** checkbox.

4.  Click **Deploy Application** for a new deployment, or **Apply Changes** for an existing
    application.

After redeployment, the Runtime Manager backend begins instrumenting traces for the application.

## Allocate Resources for the Monitoring Sidecar

Starting with Runtime Fabric agent version 3.0.0, all telemetry — metrics, logs, and traces — is
transported through a single sidecar container deployed per application replica. Allocate cluster
capacity accordingly to avoid deployment failures.

Resource requirements per replica depend on which features are enabled:

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Feature</th><th>CPU</th><th>Memory</th></tr></thead><tbody><tr><td><p>Metrics only</p></td><td><p>0.05 vCPU</p></td><td><p>90 MiB</p></td></tr><tr><td><p>Metrics + logs</p></td><td><p>Up to 30% of the app replica’s CPU limit</p></td><td><p>Up to 150 MiB</p></td></tr><tr><td><p>Metrics + logs + traces</p></td><td><p>Up to 30% of the app replica’s CPU limit</p></td><td><p>Up to 240 MiB</p></td></tr></tbody></table>

### Legacy Architecture (Runtime Fabric Agent 2.11.x and Earlier)

In Runtime Fabric agent version 2.11.x and earlier, two separate agents handled telemetry:

- One DaemonSet per node to forward logs

- One sidecar per replica to forward metrics

This architecture was replaced by the single-sidecar model in version 3.0.0.

## Disable Anypoint Monitoring

Anypoint Monitoring is enabled by default. To disable it for a specific Mule app, pass this property
at deployment time:

```bash
anypoint.platform.config.analytics.agent.enabled=false
```

> [!NOTE] Disable monitoring only if your team or organization has compliance or geospecific
> requirements that prevent sending metrics to the Anypoint control plane, and you are not
> contractually obligated to send metrics for usage and billing purposes.

## See Also

- [Monitoring Applications Deployed to Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/manage-monitor-applications)

- [Configure Logging and Log Levels](https://docs.mulesoft.com/runtime-fabric/latest/deploy-to-runtime-fabric#configure-logging-and-log-levels)

- [Migrate Log Forwarding Before Upgrading Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/migrate-log-forwarding)

- [Configure Network for Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/install-self-managed-network-configuration)