Contact Free trial Login

Supported Connection-Level Metrics

Connection-level metrics, or edge metrics, are available for many of your connections in the Anypoint 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. You may see this message in the card: Inbound/Outbound metrics are not available for this connection. Learn more.

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, Anypoint 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 Anypoint 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.

Connection Type Supported Requirements and Restrictions

Inbound Metrics

Client App Group to a Mule App

Yes

None

External Traffic to a Mule App

Yes

If there is a connection from external traffic to a Mule app and also a connection from a Mule app using Mule version 4.x released before April 14, 2020 or a Mule version with an -AM extension 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.

Mule App to a Mule App

Yes

If the source node is a CloudHub app using Mule version 4.x released before April 14, 2020 or a Mule version with an -AM extension, then metrics do not appear on that connection and the following message appears:

Inbound metrics may be inaccurate or not appear when the source of the connection is a Mule app using Mule runtime version 4.x or an -AM extension. Learn more.

Mule App to a Non-Mule Node

Not applicable

None

Outbound Metrics

Client App Group to a Mule App

Not applicable

None

External Traffic to a Mule App

Not applicable

None

Mule App to a Mule App

Yes

  • Outbound metrics on a connection are available only if the destination app is using one of these Mule versions. If not, the following message appears:

Outbound metrics are not available for this connection. You may need to update the runtime version of the destination Mule app.

  • 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:

Outbound metrics are not available for this connection. Learn more.

Mule App to a Non-Mule Node

Yes

None

Standalone Mule

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

Connection Type Supported Requirements and Restrictions

Inbound Metrics

Client App Group to a Mule App

Yes

None

External Traffic to a Mule App

Yes

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.

Mule App to a Mule App

Yes

If the following conditions exist, then metrics do not appear for a connection:

  • The source node is a standalone Mule app

  • The app uses an HTTP Connector version earlier than 1.5.12

  • The app uses a Mule 4.x version with Anypoint Monitoring Agent released before April 6, 2020

  • Additional header injection is not enabled

Additionally, the following message appears:

Inbound metrics may be inaccurate or not appear when the source of the connection is a Mule app using Mule runtime version 4.x. Learn how to view connections and their metrics properly.

Learn more about enabling the header injection.

Mule App to a Non-Mule Node

Not applicable

None

Outbound Metrics

Client App Group to a Mule App

Not applicable

None

External Traffic to a Mule App

Not applicable

None

Mule App to a Mule App

Yes

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:

Outbound metrics are not available for this connection. Learn more.

This message also appears if there has not been traffic in the selected time range.

Mule App to a Non-Mule Node

Yes

None

Runtime Fabric

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

Connection Type Supported Requirements and Restrictions

Inbound Metrics

Client App Group to a Mule App

Yes

None

External Traffic to a Mule App

Yes

None

Mule App to a Mule App

Yes

If the following conditions exist, then metrics do not appear for a connection:

  • The source node is a Runtime Fabric app

  • The app uses an HTTP Connector version earlier than 1.5.12

  • The app uses a Mule 4.x version with Anypoint Monitoring Agent released before April 6, 2020

  • Additional header injection is not enabled

Additionally, the following message appears:

Inbound metrics may be inaccurate or not appear when the source of the connection is a Mule app using Mule runtime version 4.x. Learn how to view connections and their metrics properly.

Learn more about enabling the header injection.

Mule App to a Non-Mule Node

Not applicable

None

Outbound Metrics

Client App Group to a Mule App

Not applicable

None

External Traffic to a Mule App

Not applicable

None

Mule App to a Mule App

Yes

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:

Outbound metrics are not available for this connection. Learn more.

This message also appears if there has not been traffic in the selected time range.

Mule App to a Non-Mule Node

Yes

None

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub