GangliaWriter · jmxtrans/jmxtrans Wiki · GitHub

GangliaWriter · jmxtrans/jmxtrans Wiki · GitHub

jmxtrans has a writer that connects to a gmond (not gmetad!) process and writes data directly to it using UDP. One nice feature of Ganglia is that you do not need to configure it when you add new hosts.

As described in the (borrowed) image above, you can see that jmxtrans is writing data to a gmond instance. Since I support host spoofing, whatever is set as host or optionallyalias is what is sent to Ganglia as the host. Thus, jmxtrans is effectively acting like a gmond instance itself. This also means that jmxtrans doesn't have to run on the same machine as the gmond instance. Note that for proper host spoofing Ganglia compares both the name of the host and the IP address associated with it. The GangliaWriter will attempt to resolve the address of the host (or alias) for you. If this does not work you can correctly spoof Ganglia by providing an alias value in the form that it expects, specifically IP:hostname (e.g. "10.10.10.3:myhost")

• host - The hostname for the machine running gmond.
• alias (optional) - The spoofed hostname (see documentation above).

Read full article from GangliaWriter · jmxtrans/jmxtrans Wiki · GitHub

Introduction to Ganglia on Ubuntu 14.04 | DigitalOcean

Introduction to Ganglia on Ubuntu 14.04 | DigitalOcean
On the back end, Ganglia is made up of the following components:
Gmond (Ganglia monitoring daemon): a small service that collects information about a node. This is installed on every server you want monitored.
Gmetad (Ganglia meta daemon): a daemon on the master node that collects data from all the Gmond daemons (and other Gmetad daemons, if applicable).
RRD (Round Robin Database) tool: a tool on the master node used to store data and visualizations for Ganglia in time series.
PHP web front-end: a web interface on the master node that displays graphs and metrics from data in the RRD tool.

Basically, every node (server) that you want monitored has Gmond installed. Every node uses Gmond to send data to the single master node running Gmetad, which collects all the node data and sends it to the RRD tool to be stored

sudo apt-get install -y ganglia-monitor rrdtool gmetad ganglia-webfrontend

sudo vi /etc/ganglia/gmetad.conf

Find the line that begins with data_source, as shown below:

data_source "my cluster" localhost

Edit the data_source line to list the name of your cluster, the data collection frequency in seconds, and your server's connection information. In the example below, the data source is called my cluster, and it collects metrics once a minute from the localhost (itself). You can add more data_source lines to create as many clusters as you want.

data_source "my cluster" 60 localhost

Save your changes.

Next, edit the Gmond configuration file. Even though this is the master node, we are also setting it up for monitoring as the first node in the "my cluster" cluster. The gmond.conf file configures where the node sends its information.

sudo vi /etc/ganglia/gmond.conf

In the cluster section, make sure you set the name to the same one you set in the gmetad.conf file, which in this example is my cluster. The rest of the fields are optional and can be left asunspecified.

Read full article from Introduction to Ganglia on Ubuntu 14.04 | DigitalOcean

Java mon amour: JMXTrans and Graphite: getting started

Java mon amour: JMXTrans and Graphite: getting started
I verify the installation parameters:
less /etc/sysconfig/jmxtrans 

# configuration file for package jmxtrans
export JAR_FILE="/usr/share/jmxtrans/jmxtrans-all.jar"
export LOG_DIR="/var/log/jmxtrans"
export SECONDS_BETWEEN_RUNS=60
export JSON_DIR="/var/lib/jmxtrans"
export HEAP_SIZE=512
export NEW_SIZE=64
export CPU_CORES=2
export NEW_RATIO=8
export LOG_LEVEL=debug

java -Dcom.sun.management.jmxremote.port=1105 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false Sample 

cd /usr/share/jmxtrans
./jmxtrans.sh
Usage: ./jmxtrans.sh {start|stop|restart|status} [filename.json]

01

{

02	"servers" : [ {

03	"port" : "1099",

04	"host" : "w2",

05	"queries" : [ {

06	"outputWriters" : [ {

07	"@class" : "com.googlecode.jmxtrans.model.output.StdOutWriter",

08	"settings" : {

09

}

10

} ],

11	"obj" : "java.lang:type=Memory",

12	"attr" : [ "HeapMemoryUsage", "NonHeapMemoryUsage" ]

13

}, {

14	"outputWriters" : [ {

15	"@class" : "com.googlecode.jmxtrans.model.output.StdOutWriter",

16	"settings" : {

17

}

18

} ],

19	"obj" : "java.lang:name=CMS Old Gen,type=MemoryPool",

20	"attr" : [ "Usage" ]

21

}, {

22	"outputWriters" : [ {

23	"@class" : "com.googlecode.jmxtrans.model.output.StdOutWriter",

24	"settings" : {

25

}

26

} ],

27	"obj" : "java.lang:name=ConcurrentMarkSweep,type=GarbageCollector",

28	"attr" : [ "LastGcInfo" ]

29

} ],

30	"numQueryThreads" : 2

31

} ]

32

}

/usr/share/jmxtrans/jmxtrans.sh start sample.json 
tail -f jmxtrans.log 
Read full article from Java mon amour: JMXTrans and Graphite: getting started