Skip to content

include-traffic-inspection.adoc

Latest commit

 

History

History
90 lines (78 loc) · 3.73 KB

include-traffic-inspection.adoc

File metadata and controls

90 lines (78 loc) · 3.73 KB

Intercept and inspect all HTTPS traffic through a proxy server that resides between your on-premises Mule apps and Anypoint Monitoring. To enable traffic inspection for your hybrid deployments, you must install the latest Anypoint Monitoring agent.

At this time, the Anypoint Monitoring agent that supports traffic inspection is available for Mule instances running on Linux.

  • A closed beta version of the Anypoint Monitoring agent from a Salesforce representative

    The agent’s zip file is available to a limited customer base.

  • A Mule server that is registered in Runtime Manager

    To set up a Mule server, see runtime-manager::rtm-traffic-inspection.adoc.

  • The private certificate in the proxy that communicates with the Anypont Monitoring agent in the Mule runtime instance includes us1.ingest.mulesoft.com in its Subject Alternative Name (SAN).

    In addition, you must add this private certificate or its CA certificate to the operating system’s system-wide truststore. For guidance, see Adding new certificates in the Redhat Linux documentation.

  • Access to Anypoint Monitoring

    An Anypoint Platform administrator can provide access from Access Manager, in Anypoint Platform. For more information, see monitoring::am-permissions.adoc.

To enable traffic inspection:

  1. If an Anypoint Monitoring agent is installed on your server, uninstall the agent and delete its /am subfolder:

    1. From your Mule home directory (MULE_HOME), run the following command to uninstall the agent:

      ./bin/uninstall

    2. Delete the /am subfolder from your Mule home directory.

  2. Place the Anypoint Monitoring agent zip file (am-3.x.zip) into your Mule home directory (MULE_HOME).

    The zip is available as part of the closed beta program.

  3. Extract the zip file to add the /am subfolder into your Mule home directory (MULE_HOME).

  4. From the command line:

    1. Navigate to the /am subfolder, for example:

      cd am

    2. Install the agent to your Linux server:

      ./bin/install -p http:/proxy-server:port

      Replace http:/proxy-server:port with the URI of your proxy server and port.

  5. Restart your server in Runtime Manager.

    For guidance, see runtime-manager::servers-actions.adoc

  6. Return to your /am subfolder and run the setup script:

    ./bin/setup

  7. After approximately five minutes, check for your server’s metrics in Anypoint Monitoring, within the Investigations tab of the Built-in Dashboard page for your deployment.

    To troubleshoot issues, check the log files under am/logs in your Mule home directory.

  1. Open the Hybrid settings page in Anypoint Monitoring (US, EU).

    For more guidance, see monitoring::monitoring-settings-page.adoc.
⚡