JarCastingjmxtrans
Last Version: 1.2.2
Release Date:
JmxTrans
org.jmxtrans : jmxtransJMX 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:
JmxTrans - Core
org.jmxtrans : jmxtrans-coreThis module contains most of the core logic of JmxTrans.
Last Version: 272
Release Date:
JmxTrans - utils
org.jmxtrans : jmxtrans-utilsThis module contains utilities that do not have direct dependencies on JmxTrans.
Last Version: 272
Release Date:
JmxTrans - Core output writers
org.jmxtrans : jmxtrans-output-coreThis module contains output writers that do not have any special dependencies.
Last Version: 272
Release Date:
JmxTrans - Ganglia output writers
org.jmxtrans : jmxtrans-output-gangliaThis module contains Ganglia output writers.
Last Version: 272
Release Date:
JmxTrans - JRobin output writers
org.jmxtrans : jmxtrans-output-jrobinThis module contains output writers that depends on the jrobin library.
Last Version: 272
Release Date:
JmxTrans - CloudWatch output writers
org.jmxtrans : jmxtrans-output-cloudwatchThis module contains output writers based on CloudWatch (AWS).
Last Version: 272
Release Date:
JmxTrans - ElasticSearch output writers
org.jmxtrans : jmxtrans-output-elasticThis 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:
JmxTrans - GELF output writers
org.jmxtrans : jmxtrans-output-gelfThis 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:
JmxTrans - InfluxDB output writers
org.jmxtrans : jmxtrans-output-influxdbThis module contains InfluxDB output writers.
Last Version: 272
Release Date:
JmxTrans - Kafka output writers
org.jmxtrans : jmxtrans-output-kafkaThis 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:
JmxTrans - Velocity output writers
org.jmxtrans : jmxtrans-output-velocityThis module contains output writers that use Apache Velocity template engine.
Last Version: 272
Release Date:
JmxTrans - Logback output writers
org.jmxtrans : jmxtrans-output-logbackThis module contains output writers that have direct dependencies on logging frameworks.
Last Version: 272
Release Date:
JmxTrans - Examples
org.jmxtrans : jmxtrans-examplesThis module contains examples of how to use JmxTrans. It is not included in the final packaging.
Last Version: 272
Release Date:
jmxtrans - output writers
org.jmxtrans : jmxtrans-outputThis 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:
JmxTrans - log4j output writers
org.jmxtrans : jmxtrans-output-log4jThis module contains output writers that have direct dependencies on logging frameworks.
Last Version: 269
Release Date:JMXTrans structured document output writer for Elasticsearch
com.github.vveloso : jmxtrans-output-elastic-aggregateJMXTrans output writer for Elasticsearch which outputs one structured document for each query.
Last Version: 2.2
Release Date:
JMX metrics exporter agent
org.jmxtrans.agent : jmxtrans-agentSonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/
Last Version: 1.2.11
Release Date:
cocktail-app
org.jmxtrans.embedded.samples : cocktail-appEmbedded jmxtrans demo based on a cocktail app
Last Version: 1.0.14
Release Date:
cocktail-app-infrastructure
org.jmxtrans.embedded.samples : cocktail-app-infrastructureCocktail App Infrastructure
Last Version: 1.0.14
Release Date:
embedded-jmxtrans-samples
org.jmxtrans.embedded.samples : embedded-jmxtrans-samplesEmbedded jmxtrans samples
Last Version: 1.0.14
Release Date:
JmxTrans - Docker tests
org.jmxtrans : jmxtrans-docker-testThis 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:
Last Version: 272
Release Date:
Last Version: 272
Release Date:
JmxTrans - systemd packaging
org.jmxtrans : jmxtrans-systemd.deb and .rpm packages for OS supporting systemd
Last Version: 272
Release Date:
JmxTrans - test utils
org.jmxtrans : jmxtrans-test-utilsThis module contains utilities used purely in tests.
Last Version: 272
Release Date:
Last Version: 272
Release Date:- 1