Project Group: org.jmxtrans

JmxTrans

org.jmxtrans : 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.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - Core

org.jmxtrans : jmxtrans-core

This module contains most of the core logic of JmxTrans.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - utils

org.jmxtrans : jmxtrans-utils

This module contains utilities that do not have direct dependencies on JmxTrans.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - Core output writers

org.jmxtrans : jmxtrans-output-core

This module contains output writers that do not have any special dependencies.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - JRobin output writers

org.jmxtrans : jmxtrans-output-jrobin

This module contains output writers that depends on the jrobin library.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - Ganglia output writers

org.jmxtrans : jmxtrans-output-ganglia

This module contains Ganglia output writers.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - ElasticSearch output writers

org.jmxtrans : jmxtrans-output-elastic

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.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - GELF output writers

org.jmxtrans : jmxtrans-output-gelf

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.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - InfluxDB output writers

org.jmxtrans : jmxtrans-output-influxdb

This module contains InfluxDB output writers.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - Kafka output writers

org.jmxtrans : jmxtrans-output-kafka

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.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - Velocity output writers

org.jmxtrans : jmxtrans-output-velocity

This module contains output writers that use Apache Velocity template engine.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - CloudWatch output writers

org.jmxtrans : jmxtrans-output-cloudwatch

This module contains output writers based on CloudWatch (AWS).

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - Logback output writers

org.jmxtrans : jmxtrans-output-logback

This module contains output writers that have direct dependencies on logging frameworks.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - Examples

org.jmxtrans : jmxtrans-examples

This module contains examples of how to use JmxTrans. It is not included in the final packaging.

Last Version: 272

Release Date: Mar 30, 2021

jmxtrans - output writers

org.jmxtrans : jmxtrans-output

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.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - test utils

org.jmxtrans : jmxtrans-test-utils

This module contains utilities used purely in tests.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - packaging

org.jmxtrans : jmxtrans-packaging

Parent module of new jmxtrans packaging.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - systemd packaging

org.jmxtrans : jmxtrans-systemd

.deb and .rpm packages for OS supporting systemd

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - Docker tests

org.jmxtrans : jmxtrans-docker-test

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.

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - parent project

org.jmxtrans : jmxtrans-parent

JMX metrics exporter

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - Web App

org.jmxtrans : jmxtrans-webapp

Run JMXTrans as a web application/

Last Version: 272

Release Date: Mar 30, 2021

JmxTrans - log4j output writers

org.jmxtrans : jmxtrans-output-log4j

This module contains output writers that have direct dependencies on logging frameworks.

Last Version: 269

Release Date: Mar 9, 2018