This extension works only with the standalone machine agent.
Mule ESB is a lightweight Java-based enterprise service bus (ESB) and integration platform that allows developers to connect applications together quickly and easily, enabling them to exchange data. This extension monitors Mule ESB instance and collects useful statistics exposed through MBeans and reports to AppDynamics Controller.
Before the extension is installed, the prerequisites mentioned here need to be met. Please do not proceed with the extension installation if the specified prerequisites are not met.
To use this extension please configure JMX in Mule ESB instance. To configure JMX please add following properties to the wrapper.conf of the Mule instance.
###JMX Connection Properties### wrapper.java.additional.5=-Dcom.sun.management.jmxremote wrapper.java.additional.6=-Dcom.sun.management.jmxremote.port=9000 wrapper.java.additional.7=-Dcom.sun.management.jmxremote.authenticate=false wrapper.java.additional.8=-Dcom.sun.management.jmxremote.ssl=false wrapper.java.additional.9=-Djava.rmi.server.hostname=localhost
In the AppDynamics Metric Browser, look for: Application Infrastructure Performance | <Tier> | Custom Metrics | Mule ESB in case of default metric path
Note : Please make sure not to use tab (\t) while editing yaml files. You can validate the yaml file using a yaml validator
<MachineAgent_Dir>/monitors/The metricPrefix of the extension has to be configured as specified here. Please make sure that the right metricPrefix is chosen based on your machine agent deployment, otherwise this could lead to metrics not being visible in the controller.
We can exclude domains by specifying them in the
excludeDomains configuration. For eg.
# Mule ESB instance particulars server: host: "localhost" port: 9000 username: "" password: "" # Mule ESB MBeans mbeans: domainMatcher: "Mule.*" types: [org.mule.Statistics] excludeDomains: [Mule..agent,Mule.default] #prefix used to show up metrics in AppDynamics metricPrefix: "Custom Metrics|Mule ESB|"
Configure the path to the config.yml file by editing the in the monitor.xml file in the
<MACHINE_AGENT_HOME>/monitors/MuleESBMonitor/ directory. Below is the sample
<task-arguments> <!-- config file--> <argument name="config-file" is-required="true" default-value="monitors/MuleESBMonitor/config.yml" /> .... </task-arguments>
Please look at the troubleshooting document and make sure that everything is followed correctly.
Always feel free to fork and contribute any changes directly via GitHub.
For any support questions, please contact email@example.com.
Mule ESB Version: