Contact Free trial Login

Manage Performance and Data Collection

Anypoint Visualizer collects runtime information from running applications, APIs, and proxies to detect all of its dependencies. The information collected includes IP address and URL (without parameters) of the incoming request, as well as URL (without parameters), and some header values of outgoing requests. This information is encrypted and stored in a database.

Metadata Description

node_info

General information about the node.

org_id

The organization where the node is deployed.

ip

The IP address of the node.

type

Specifies whether the node is an API or Mule application.

deployment_id

An internal ID that specifies the hash of the application or API.

app_name

The name of the application.

url

The fully qualified domain of the application.

The agent that Anypoint Visualizer uses to collect metadata may have a performance impact.

Reduce Potential Performance Impact for CloudHub

To reduce any potential performance impact for an application running in CloudHub, you can disable data collection and the Anypoint Monitoring agent.

Disable Data Collection in CloudHub

If you are using the following Mule versions, you can disable data collection by setting an application property:

  • Mule Version 4 Released Before March 22, 2019

  • Mule Version 3.9 Released Before April 5, 2019

    1. Set the application property anypoint.platform.config.visualizer.agent.enabled=false.

    2. Redeploy the application.

Disable the Anypoint Monitoring agent in CloudHub

If you are using the following Mule versions, you can disable the Anypoint Monitoring agent:

  • Mule Version 4 Released on March 22, 2019 or Later

  • Mule Version 3.9 Released on April 5, 2019 or Later

  • Mule Version 3.8.7 Released on August 14, 2019 or Later

    1. Verify that you are a user with Anypoint Monitoring User permission.

    2. Sign in to Anypoint Platform and click Anypoint Monitoring.

    3. Click Settings.

    4. Select CloudHub.

    5. From the Environment drop-down list, choose an environment.

    6. In List of resources in <Environment Name>, search for an application whose metrics you wish to see.

    7. Next to application, click Disable & Apply to disable monitoring for the application.

Reduce Potential Performance Impact for Standalone Mule

Visualizer requires an additional header injection to work for standalone Mule deployments. To reduce potential performance impact for applications running in a standalone instance of Mule 4.1.x, the header injection is disabled by default.

To disable the header injection for Mule 3, set the following property:

anypoint.platform.config.analytics.agent.header_injection.disabled=true

Additionally, to reduce potential performance impact for applications running in a standalone instance of Mule, you can do one of the following:

  • Deploy the application to a server without the Anypoint Monitoring agent installed.

  • Disable data collection for a specific server. To disable data collection for a server and all the applications deployed to that server, set the following property at the server level (not the application level):

    anypoint.platform.config.analytics.agent.disabled=true
This disables monitoring for applications on the server as well.

Reduce Potential Performance Impact for Runtime Fabric

Anypoint Visualizer requires an additional header injection to work for Runtime Fabric deployments. To reduce potential performance impact for applications, the header injection is disabled by default. For Runtime Fabric, you must enable header injection at the application level.

To disable the header injection for Mule 3, set the following property:

anypoint.platform.config.analytics.agent.header_injection.disabled=true

We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used and to tailor advertising. You can read more and make your cookie choices here. By continuing to use this site you are giving us your consent to do this.