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.

License

License

Categories

Categories

jmxtrans Application Testing & Monitoring Monitoring
GroupId

GroupId

org.jmxtrans
ArtifactId

ArtifactId

jmxtrans-output
Last Version

Last Version

272
Release Date

Release Date

Type

Type

pom
Description

Description

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.
Project Organization

Project Organization

JmxTrans team

Download jmxtrans-output

Filename Size
jmxtrans-output-272.pom 2 KB
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/org.jmxtrans/jmxtrans-output/ -->
<dependency>
    <groupId>org.jmxtrans</groupId>
    <artifactId>jmxtrans-output</artifactId>
    <version>272</version>
    <type>pom</type>
</dependency>
// https://jarcasting.com/artifacts/org.jmxtrans/jmxtrans-output/
implementation 'org.jmxtrans:jmxtrans-output:272'
// https://jarcasting.com/artifacts/org.jmxtrans/jmxtrans-output/
implementation ("org.jmxtrans:jmxtrans-output:272")
'org.jmxtrans:jmxtrans-output:pom:272'
<dependency org="org.jmxtrans" name="jmxtrans-output" rev="272">
  <artifact name="jmxtrans-output" type="pom" />
</dependency>
@Grapes(
@Grab(group='org.jmxtrans', module='jmxtrans-output', version='272')
)
libraryDependencies += "org.jmxtrans" % "jmxtrans-output" % "272"
[org.jmxtrans/jmxtrans-output "272"]

Dependencies

test (2)

Group / Artifact Type Version
ch.qos.logback : logback-classic jar 1.2.3
ch.qos.logback : logback-core jar 1.2.3

Project Modules

  • jmxtrans-output-cloudwatch
  • jmxtrans-output-core
  • jmxtrans-output-ganglia
  • jmxtrans-output-jrobin
  • jmxtrans-output-logback
  • jmxtrans-output-velocity
  • jmxtrans-output-kafka
  • jmxtrans-output-elastic
  • jmxtrans-output-influxdb
  • jmxtrans-output-gelf

jmxtranslogo

FOSSA Status Build Status Build status Dependency Status Gitter Maven site Maven Central sonarcloud.io

This is the source code repository for the jmxtrans project.

This is effectively the missing connector between speaking to a JVM via JMX on one end and whatever logging / monitoring / graphing package that you can dream up on the other end.

jmxtrans is very powerful tool which uses easily generated JSON (or YAML) based configuration files and then outputs the data in whatever format you desire. It does this with a very efficient engine design that will scale to communicating with thousands of machines from a single jmxtrans instance.

The core engine is very solid and there are writers for Graphite, StatsD, Ganglia, cacti/rrdtool, OpenTSDB, text files, and stdout. Feel free to suggest more on the discussion group or issue tracker.

Coda Hale did an excellent talk for Pivotal Labs on why metrics matter. Great justification for using a tool like jmxtrans.

render

Special thanks:

License

FOSSA Status

org.jmxtrans

jmxtrans project

Versions

Version
272
271
270
269
268
267
266
265
264
263
262
261
260
259
256
254
253
252
251