WildFly Transaction Manager Monitoring: Difference between revisions
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
* [[WildFly Monitoring#Metrics|WildFly Monitoring]] | * [[WildFly Monitoring#Metrics|WildFly Monitoring]] | ||
=Relevance= | |||
* EAP 6.4.10 | |||
=Activation= | =Activation= | ||
| Line 9: | Line 13: | ||
=JMX Monitoring= | =JMX Monitoring= | ||
JTA transaction statistics can be collected from the JBoss “transactions” subsystem, using the following JMX ObjectName: | |||
<pre> | |||
jboss.as:subsystem=transactions | |||
</pre> | |||
The following JMX attributes are available: | |||
==JMX Attributes== | ==JMX Attributes== | ||
Latest revision as of 15:52, 11 May 2017
Internal
Relevance
- EAP 6.4.10
Activation
Statistics must be explicitly enabled.
JMX Monitoring
JTA transaction statistics can be collected from the JBoss “transactions” subsystem, using the following JMX ObjectName:
jboss.as:subsystem=transactions
The following JMX attributes are available: