DataDog and JMX: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 59: | Line 59: | ||
* [[JMX_Access_to_EAP_7_Host_Controller#URL|For EAP 7 Host Controller]] | * [[JMX_Access_to_EAP_7_Host_Controller#URL|For EAP 7 Host Controller]] | ||
* [[JMX_Access_to_Domain_Mode_EAP_7_Server_Node#URL|For EAP 7 Domain Mode Server Node]] | * [[JMX_Access_to_Domain_Mode_EAP_7_Server_Node#URL|For EAP 7 Domain Mode Server Node]] | ||
=Troubleshooting= | |||
Revision as of 14:57, 19 October 2016
External
Internal
Configuration
The JMX configuration is located in /etc/dd-agent/conf.d/jmx.yaml.example.
After modification and removal of the ".example" suffix, restart datadog as root:
service datadog-agent restart
JMX integration with JBoss
Server Preparation
JBoss instances have to be configured to allow JMX agent access. Details on how to configure JBoss various JBoss versions running in various modes are available here:
Agent Classpath and Startup Options
The agent must include the following classpath:
-Djava.class.path=${JAVA_HOME}/lib/jconsole.jar:${JAVA_HOME}/lib/tools.jar:${JBOSS_HOME}/bin/client/jboss-cli-client.jar
The agent must also receive the following system property on command line:
-Dmodule.path=${JBOSS_HOME}/modules
The full command line is:
jconsole \
-J-Djava.class.path=${JAVA_HOME}/lib/jconsole.jar:${JAVA_HOME}/lib/tools.jar:${JBOSS_HOME}/bin/client/jboss-cli-client.jar \
-J-Dmodule.path=${JBOSS_HOME}/modules
Connect to the JBoss Instance
Use the following URLs:
- For Standalone EAP 6
- For EAP 6 Host Controller
- For EAP 6 Domain Mode Server Node
- For Standalone EAP 7
- For EAP 7 Host Controller
- For EAP 7 Domain Mode Server Node