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 3.x version of Anypoint Monitoring agent.
At this time, the Anypoint Monitoring agent that supports traffic inspection is available for Mule instances running on Red Hat Enterprise Linux (RHEL) 7 and later.
-
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.
-
Traffic inspection is enabled for your on-premise Mule instances
For guidance, 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.comin 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:
-
If an earlier version of Anypoint Monitoring agent is installed on your server, uninstall the agent and delete its
amsubfolder:-
From your agent’s home directory (
${AM_HOME}, typically${MULE_HOME}/am), run this command to uninstall the agent:./bin/uninstall
-
Delete the
amsubfolder from your Mule home directory (${MULE_HOME}).
-
-
Place the Anypoint Monitoring agent zip file (
am-3.x.zip) into${MULE_HOME}.The zip is available as part of the closed beta program.
-
Extract the zip file to add the
amsubfolder into your Mule home directory (${MULE_HOME}). -
From the command line:
-
Navigate to the
amsubfolder, for example:cd am
-
Install the agent to your Linux server:
./bin/install -p http:/proxy-server:port
Replace
http:/proxy-server:portwith the URI of your proxy server and port.
-
-
Restart your server in Runtime Manager.
For guidance, see runtime-manager::servers-actions.adoc
-
From your
amsubfolder, run the setup script:./bin/setup
-
After approximately five minutes, check for your Mule app’s metrics in Anypoint Monitoring:
From Anypoint Monitoring (requires login), select your Environment (such as Sandbox or Production) and the Resource name of your hybrid Mule app to display the app’s monitoring data.
To troubleshoot issues, check the log files under
am/logsin your Mule home directory.