Group: org.jmxtrans - All Dependencies
JmxTrans - test utils · This module contains utilities used purely in tests.
JmxTrans - Core · This module contains most of the core logic of JmxTrans.
JmxTrans - utils · This module contains utilities that do not have direct dependencies on JmxTrans.
JmxTrans - Core output writers · This module contains output writers that do not have any special dependencies.
JmxTrans - JRobin output writers · This module contains output writers that depends on the jrobin library.
JmxTrans - Ganglia output writers · This module contains Ganglia output writers.
JmxTrans - Velocity output writers · This module contains output writers that use Apache Velocity template engine.
JmxTrans - Kafka output writers
JmxTrans - CloudWatch output writers · This module contains output writers based on CloudWatch (AWS).
JmxTrans - InfluxDB output writers · This module contains InfluxDB output writers.
JmxTrans - ElasticSearch output writers
JmxTrans - GELF output writers
JmxTrans - Logback output writers · This module contains output writers that have direct dependencies on logging frameworks.
JmxTrans · JMX metrics exporter. This module creates the packaging for JmxTrans. It does not contain any application code, but creates .deb, .rpm or other packaging.
JmxTrans - log4j output writers · This module contains output writers that have direct dependencies on logging frameworks.
jmxtrans - output writers · This module groups all different output writers. Different output writers have different dependencies. To ensure that those dependencies do not leak to other output writer, or that we can limit to number of dependencies at runtime, output writers are split into separate modules based on the dependencies they use. For example, the CloudWatch output writers depends on the AWS SDK, which is quite large and not used by any other output writer. If you only want to send metrics to Graphite, there should be no need to have the AWS SDK in your classpath at runtime. Some dependencies are also problematic. They can introduce incompatibilities. For example, a few writers are based directly on log4j or logback. This direct dependence breaks the use of SLF4J. By isolating those output writers to a specific module, we can ensure this has minimal impact.
JmxTrans - Examples · This module contains examples of how to use JmxTrans. It is not included in the final packaging.
JmxTrans - Docker tests · This module contains integration of Deb and RPM packages. It uses Docker to check that these packages install properly on various Linux distributions. It is not included in the final packaging.
JmxTrans - systemd packaging · .deb and .rpm packages for OS supporting systemd
JmxTrans - packaging · Parent module of new jmxtrans packaging.
