---
schema_version: "1"
id: 05a8f8fc7faea285f9a46d51a36083cf03031759401bfed11cb70aceafa176a0
title: Supported Connection-Level Metrics in API Visualizer
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/visualizer/connection-metrics-compatibility.md
canonical_url: https://docs.mulesoft.com/visualizer/connection-metrics-compatibility
source_site: docs.mulesoft.com
content_type: documentation
content_hash: cd9eb6642844d4c36f284e882510a0293da2ccbeae4154fecdbe0ecb24b0a16e
description: MuleSoft Documentation Site
latest: true
---
---
product: API Visualizer
---

# Supported Connection-Level Metrics in API Visualizer

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

Connection-level metrics, or _edge metrics_, are available for many of your connections in the API
Visualizer canvas. Depending on your deployment type (CloudHub, standalone Mule, or Runtime Fabric),
some inbound or outbound metrics do not appear at the connection level. You can use this guide to
determine why metrics are absent from your canvas.

Metric is Not Available

Connections appear if there has been traffic between those services in the past 7 days. If there was
no traffic for a particular edge in the time range selected on the **Metric** card, however, metrics
will not appear on that edge. This message might appear in the card:
`Inbound/Outbound metrics are not available for this connection. Learn more.`

> [!NOTE] You may also see the same message if you are using a dedicated load balancer. See below.

Metric is Not Applicable

If support for a type of metric on a connection level is listed as _not applicable_, API Visualizer
does not have access to the data associated with this connection type. For example, you have
selected inbound average response time and have a Mule app calling Salesforce. This metric refers to
the average time that Salesforce took to respond to the inbound call. This is not data that API
Visualizer currently registers. In this case, the following message appears:
`Inbound/Outbound metrics are not applicable for this type of connection.`

## CloudHub

The following connection types and directions support or do not support connection-level metrics,
depending on the specified requirements and restrictions.

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Connection Type</th><th>Supported</th><th>Requirements and Restrictions</th></tr></thead><tbody><tr><td colspan="3"><p><strong>Inbound Metrics</strong></p></td></tr><tr><td><p>Client App Group to a Mule App</p></td><td><p>Yes</p></td><td><p>None</p></td></tr><tr><td><p>External Traffic to a Mule App</p></td><td><p>Yes</p></td><td><p>None</p></td></tr><tr><td><p>Mule App to a Mule App</p></td><td><p>Yes</p></td><td><p>If there has not been traffic in the selected time range, the following message appears: <code>Inbound metrics are not available for this connection. Learn more.</code></p></td></tr><tr><td><p>Mule App to a Non-Mule Node</p></td><td><p>Not applicable</p></td><td><p>None</p></td></tr><tr><td colspan="3"><p><strong>Outbound Metrics</strong></p></td></tr><tr><td><p>Client App Group to a Mule App</p></td><td><p>Not applicable</p></td><td><p>None</p></td></tr><tr><td><p>External Traffic to a Mule App</p></td><td><p>Not applicable</p></td><td><p>None</p></td></tr><tr><td><p>Mule App to a Mule App</p></td><td><p>Yes</p></td><td><div><div><ul><li><p>Outbound metrics on a connection are available only if the destination app is using one of these <a href="https://docs.mulesoft.com/visualizer/cloudhub-setup#verify-supported-mule-runtime-engine-mule-versions-for-metrics">Mule versions</a>. If not, the following message appears:</p></li></ul></div><div><p><code>Outbound metrics are not available for this connection. Update the runtime version of the destination Mule app.</code></p></div><div><ul><li><p>If the dedicated load balancer (DLB) modifies the URL, then metrics are not available for any of the connections passing through the DLB and the following message appears:</p></li></ul></div><div><p><code>Outbound metrics are not available for this connection. Learn more.</code></p></div></div></td></tr><tr><td><p>Mule App to a Non-Mule Node</p></td><td><p>Yes</p></td><td><p>None</p></td></tr></tbody></table>

## Standalone Mule

The following connection types and directions support or do not support connection-level metrics,
depending on the specified requirements and restrictions.

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Connection Type</th><th>Supported</th><th>Requirements and Restrictions</th></tr></thead><tbody><tr><td colspan="3"><p><strong>Inbound Metrics</strong></p></td></tr><tr><td><p>Client App Group to a Mule App</p></td><td><p>Yes</p></td><td><p>None</p></td></tr><tr><td><p>External Traffic to a Mule App</p></td><td><p>Yes</p></td><td><p>If there is a connection from external traffic to a Mule app and also a connection from a Mule app using Mule 4.x to the same app, then the Mule-app-to-Mule-app edge metric does not appear; rather, it is averaged into the value shown on the edge from external traffic.</p></td></tr><tr><td><p>Mule App to a Mule App</p></td><td><p>Yes</p></td><td><p>If there has not been traffic in the selected time range, the following message appears: <code>Inbound metrics are not available for this connection. Learn more.</code></p></td></tr><tr><td><p>Mule App to a Non-Mule Node</p></td><td><p>Not applicable</p></td><td><p>None</p></td></tr><tr><td colspan="3"><p><strong>Outbound Metrics</strong></p></td></tr><tr><td><p>Client App Group to a Mule App</p></td><td><p>Not applicable</p></td><td><p>None</p></td></tr><tr><td><p>External Traffic to a Mule App</p></td><td><p>Not applicable</p></td><td><p>None</p></td></tr><tr><td><p>Mule App to a Mule App</p></td><td><p>Yes</p></td><td><p>If the dedicated load balancer (DLB) modifies the URL, then metrics are not available for any of the connections passing through the DLB and the following message appears:</p><p><code>Outbound metrics are not available for this connection. Learn more.</code></p><p>This message also appears if there has not been traffic in the selected time range.</p></td></tr><tr><td><p>Mule App to a Non-Mule Node</p></td><td><p>Yes</p></td><td><p>None</p></td></tr></tbody></table>

## Runtime Fabric

The following connection types and directions support or do not support connection-level metrics,
depending on the specified requirements and restrictions.

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Connection Type</th><th>Supported</th><th>Requirements and Restrictions</th></tr></thead><tbody><tr><td colspan="3"><p><strong>Inbound Metrics</strong></p></td></tr><tr><td><p>Client App Group to a Mule App</p></td><td><p>Yes</p></td><td><p>None</p></td></tr><tr><td><p>External Traffic to a Mule App</p></td><td><p>Yes</p></td><td><p>None</p></td></tr><tr><td><p>Mule App to a Mule App</p></td><td><p>Yes</p></td><td><p>If there has not been traffic in the selected time range, the following message appears: <code>Inbound metrics are not available for this connection. Learn more.</code></p></td></tr><tr><td><p>Mule App to a Non-Mule Node</p></td><td><p>Not applicable</p></td><td><p>None</p></td></tr><tr><td colspan="3"><p><strong>Outbound Metrics</strong></p></td></tr><tr><td><p>Client App Group to a Mule App</p></td><td><p>Not applicable</p></td><td><p>None</p></td></tr><tr><td><p>External Traffic to a Mule App</p></td><td><p>Not applicable</p></td><td><p>None</p></td></tr><tr><td><p>Mule App to a Mule App</p></td><td><p>Yes</p></td><td><p>If the dedicated load balancer (DLB) modifies the URL, then metrics are not available for any of the connections passing through the DLB and the following message appears:</p><p><code>Outbound metrics are not available for this connection. Learn more.</code></p><p>This message also appears if there has not been traffic in the selected time range.</p></td></tr><tr><td><p>Mule App to a Non-Mule Node</p></td><td><p>Yes</p></td><td><p>None</p></td></tr></tbody></table>