Configuring Monitoring
How to monitor transaction statistics

As of release 5.0, monitoring is mostly done via the log files so it integrates with your Splunk (or other) log aggregation tools. The reasoning behind this change is to make it easier to support centralised monitoring of clustered applications. JMX tends to make this more difficult because it requires per-JVM connectivity.

How to enable monitoring

All you need to do is:

  1. Add the transactions-monitoring-x.y.z.jar to your classpath (where x.y.z is the particular release you use)
  2. In your favourite logging framework, configure the log level as described below

Monitoring OLTP system health

You can monitor the OLTP system health by setting the log level for com.atomikos.monitoring.SystemHealthMonitor to INFO.

This replaces the pre-5.0 JMX monitoring of the old JmxTransactionManagerBean and displays per-JVM statistics rather than individual transaction data (to keep a useful overview).

Monitoring the connection pools

You can monitor the connection pools by setting the log level for com.atomikos.monitoring.ConnectionPoolMonitor to DEBUG.

Monitoring OLTP activity

You can monitor per-transaction OLTP activity by setting the log level for com.atomikos.monitoring.OltpMonitor to DEBUG or even TRACE.

Monitoring recovery

You can monitor recovery activity by setting the log level for com.atomikos.monitoring.RecoveryMonitor to DEBUG.

Using JMX

JMX is still supported for JDBC and JMS on a per-JVM basis - with MBeans com.atomikos.jmx.jdbc.JmxAtomikosDataSourceBean and com.atomikos.jmx.jms.JmxAtomikosConnectionFactoryBean (both in module transactions-jmx-x.y.z.jar).

Available to customers only - want a free trial?

Free Trial

Contact Us

Atomikos Corporate Headquarters
Hoveniersstraat, 39/1, 2800
Mechelen, Belgium

E info@atomikos.com
E sales@atomikos.com
T +3215613055

Subscribe to our newsletter

Never miss an update

Copyright 2020 Atomikos BVBA
This website is using cookies. More info. That's Fine