Oracle WebLogic Server is an application server for building and deploying enterprise Java EE applications. This extension aims to provide JMX monitoring capabilities for WebLogic servers and reports useful statistics to AppDynamics Controller.
This extension works only with the standalone machine agent.
WL_HOME\lib\where WL_HOME is the directory in which you installed WebLogic Server. Copy these jars to
<MachineAgent_Dir>/monitors/WebLogicMonitorThe 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.
In the AppDynamics Metric Browser, look for: Application Infrastructure Performance | <Tier> | Custom Metrics | WebLogic 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
Specify the WebLogic parameters in the config.yml.
servers: - displayName: "Server1" jmxServiceUrl: "service:jmx:t3://<host>:<port>/jndi/weblogic.management.mbeanservers.runtime" username: "weblogic" password: "admin123" jmx.remote.protocol.provider.pkgs: "weblogic.management.remote" jmx.remote.x.request.waiting.timeout: 10000 mbeans: - objectName: "com.bea:ServerRuntime=AdminServer,Name=AdminServer,Type=JVMRuntime" metricPathFromObjectNameProperties: ["Name", "Type"] metrics: include: - HeapSizeMax : "HeapSizeMax" - HeapSizeCurrent : "HeapSizeCurrent" - HeapFreeCurrent : "HeapFreeCurrent" - objectName: "com.bea:ServerRuntime=AdminServer,Name=AdminServer,Type=JTARecoveryRuntime,JTARuntime=JTARuntime" metricPathFromObjectNameProperties: ["Name", "Type", "JTARuntime"] metrics: include: - InitialRecoveredTransactionTotalCount: "InitialRecoveredTransactionTotalCount" # number of concurrent tasks numberOfThreads: 3 metricPrefix: "Custom Metrics|WebLogic|"
Workbench is an inbuilt feature provided with each extension in order to assist you to fine tune the extension setup before you actually deploy it on the controller. Please review the following document on How to use the Extensions WorkBench
You can use this extension to get all metrics that are available through the JMX interface. In order to do so though, you will have to make sure that all metrics are defined correctly. Please follow the next step in order to get this right.
You will have to list each mBean separately in the config.yml file. For each mBean you will have to add an objectName,metricPathFromObjectNameProperties and metrics tag. The following example shows exactly how you should do that. You will have to add each object name property to metricPathFromObjectNameProperties that is listed in the objectName for metric tree hierarchy. Under metrics is where you have the ability to include all the metrics that you would like to monitor.
mbeans: - objectName: "com.bea:ServerRuntime=AdminServer,Name=AdminServer,Type=JVMRuntime" metricPathFromObjectNameProperties: ["Name", "Type"] metrics: include: - HeapSizeMax : "HeapSizeMax" - HeapSizeCurrent : "HeapSizeCurrent" - HeapFreeCurrent : "HeapFreeCurrent"
Note : By default, a Machine agent or a AppServer agent can send a fixed number of metrics to the controller. To change this limit, please follow the instructions mentioned here. For eg.
java -Dappdynamics.agent.maxMetrics=2500 -jar machineagent.jar
./jconsole -J-Djava.class.path=$JAVA_HOME/lib/jconsole.jar:$WL_HOME/server/lib/wljmxclient.jar -J-Djmx.remote.protocol.provider.pkgs=weblogic.management.remote
In the dialog box, enter the URL with host, port(
service:jmx:t3://<host>:<port>/jndi/weblogic.management.mbeanservers.runtime), username and password to check the JMX connectivity.
Always feel free to fork and contribute any changes directly via GitHub.
For any questions or feature request, please contact AppDynamics Support.