---
schema_version: "1"
id: ca6b1e0ea28c532ad34649791d90b91b521d453b487374f16718992fdc306d6e
title: Managing Performance and Data Collection
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/visualizer/manage-performance.md
canonical_url: https://docs.mulesoft.com/visualizer/manage-performance
source_site: docs.mulesoft.com
content_type: documentation
content_hash: ad786b4bc1940cdd0655703c6abbd6a82b9afdefbf3f590e5e151822939ba74b
description: MuleSoft Documentation Site
latest: true
---
---
product: API Visualizer
---

# Managing Performance and Data Collection

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

API 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.

<table><colgroup><col> <col></colgroup><thead><tr><th>Metadata</th><th>Description</th></tr></thead><tbody><tr><td><p>node_info</p></td><td><p>General information about the node.</p></td></tr><tr><td><p>org_id</p></td><td><p>The organization where the node is deployed.</p></td></tr><tr><td><p>ip</p></td><td><p>The IP address of the node.</p></td></tr><tr><td><p>type</p></td><td><p>Specifies whether the node is an API or Mule application.</p></td></tr><tr><td><p>deployment_id</p></td><td><p>An internal ID that specifies the hash of the application or API.</p></td></tr><tr><td><p>app_name</p></td><td><p>The name of the application.</p></td></tr><tr><td><p>url</p></td><td><p>The fully qualified domain of the application.</p></td></tr></tbody></table>

The agent that API 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’re using this Mule version, you can disable data collection by setting an application
property:

- Mule Version 4 Released Before March 22, 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’re using this Mule version, you can disable the Anypoint Monitoring agent:

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

  1.  Log in to Anypoint Platform using an account that has the Anypoint Monitoring User permission.

  2.  In the navigation bar or the main Anypoint Platform screen, click **API Visualizer**.

  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
      want to see.

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

## Reduce Potential Performance Impact for Standalone Mule

API Visualizer requires an additional header injection to work for standalone Mule deployments.

To disable the additional header injection, 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

> [!NOTE] This disables monitoring for applications on the server as well.

## Reduce Potential Performance Impact for Runtime Fabric

API Visualizer requires an additional header injection to work for Runtime Fabric deployments.

To disable the additional header injection, set the following property:

anypoint.platform.config.analytics.agent.header\_injection.disabled=true