Everything is a Freaking DNS problem - collectd http://127.0.0.1:8080/blog/taxonomy/term/1473/0 en Graphite, JMXTrans, Ganglia, Logster, Collectd, say what ? http://127.0.0.1:8080/blog/graphite-jmxtrans-ganglia-logster-collectd-say-what <p>Given that @patrickdebois is working on improving data collection I thought it would be a good idea to describe the setup I currently have hacked together.</p> <p>(Something which can be used as a starting point to improve stuff, and I have to write documentation anyhow) </p> <p>I currently have 3 sources , and one target, which will eventually expand to at least another target and most probably more sources too.</p> <p><img src="http://www.krisbuytaert.be/images/VagrantGraphite.jpg" /></p> <p>The 3 sources are basically typical system data which I collect using collectd, However I`m using collectd-carbon from <a href="https://github.com/indygreg/collectd-carbon.git" title="https://github.com/indygreg/collectd-carbon.git">https://github.com/indygreg/collectd-carbon.git</a> to send data to Graphite.</p> <p>I`m parsing the Apache and Tomcat logfiles with logster , currently sending them only to Graphite, but logster has an option to send them to Ganglia too.</p> <p>And I`m using JMXTrans to collect JMX data from Java apps that have this data exposed and send it to Graphite. (JMXTrans also comes with a Ganglia target option) </p> <p>Rather than going in depth over the config it's probably easier to point to a Vagrant box I build <a href="https://github.com/KrisBuytaert/vagrant-graphite" title="https://github.com/KrisBuytaert/vagrant-graphite">https://github.com/KrisBuytaert/vagrant-graphite</a> which brings up a machine that does pretty much all of this on localhost.</p> <p>Obviously it's still a work in progress and lots of classes will need to be parametrized and cleaned up. But it's a working setup, and not just on my machine .. </p> http://127.0.0.1:8080/blog/graphite-jmxtrans-ganglia-logster-collectd-say-what#comments collectd devops ganglia graphite jmxtrans logster monitoringsucks Tue, 03 Jan 2012 20:46:47 +0000 Kris Buytaert 1058 at http://127.0.0.1:8080/blog #monitoringsucks and we'll fix it ! http://127.0.0.1:8080/blog/monitoringsucks-and-well-fix-it <p>If you are hacking on monitoring solutions, and want to talk to your peers solving the problem<br /> Block the monday and tuesday after fosdem in your calendar !</p> <p>That's right on february 6 and 7 a bunch of people interrested to fix the problem will be meeting , discussing and hacking stuff together in Antwerp</p> <p>In short a #monitoringsucks hackathon</p> <p>Inuits is opening up their offices for everybody who wants to join the effort Please let us (@KrisBuytaert and @patrickdebois) know if you want to join us in Antwerp</p> <p>Obviously if you can't make it to Antwerp you can join the effort on ##monitoringsucks on Freenode or on Twitter.</p> <p>The <a href="http://www.inuits.eu/contact" rel="nofollow">location will be Duboistraat 50 , Antwerp</a><br /> It is about 10 minutes walk from the Antwerp Central Trainstation<br /> Depending on Traffic Antwerp is about half an hour north of Brussels and there are hotels at walking distance from the venue.</p> <p>Plenty of parking space is available on the other side of the Park</p> http://127.0.0.1:8080/blog/monitoringsucks-and-well-fix-it#comments collectd devops ganglia graphite icinga monitoring monitoringsucks munin nagios rrd Tue, 03 Jan 2012 18:23:00 +0000 Kris Buytaert 1057 at http://127.0.0.1:8080/blog