<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Munin on cd ~</title><link>https://www.rottenbytes.info/tags/munin/</link><description>Recent content in Munin on cd ~</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 May 2010 09:28:37 +0000</lastBuildDate><atom:link href="https://www.rottenbytes.info/tags/munin/index.xml" rel="self" type="application/rss+xml"/><item><title>Switching from munin to collectd</title><link>https://www.rottenbytes.info/2010/05/20/switching-from-munin-to-collectd/</link><pubDate>Thu, 20 May 2010 09:28:37 +0000</pubDate><guid>https://www.rottenbytes.info/2010/05/20/switching-from-munin-to-collectd/</guid><description>&lt;p&gt;&lt;a href="http://www.rottenbytes.info/wp-content/uploads/2009/02/eth0.jpg"&gt;&lt;img class="size-full wp-image-62 alignleft" title="eth0" src="http://www.rottenbytes.info/wp-content/uploads/2009/02/eth0.jpg" alt="eth0" width="80" height="103" /&gt;&lt;/a&gt;Readers of this little blog may know I’ve spent some time to have a munin setup that was tweaked to be optimized. But I’ve reached a point where my knowledge did not suffice to balance the design problems of munin. This is not a rant, I just say that when your infrastructure reaches a certain size munin reaches its limits. The pull based model, the graph generation (don’t tell me about the CGI graph, this thing never worked as expected) overloaded my management box. Talking with other peoples brought collectd to my attention so I gave it a try.&lt;/p&gt;</description></item><item><title>When puppet meets nginx</title><link>https://www.rottenbytes.info/2010/02/22/when-puppet-meets-nginx/</link><pubDate>Mon, 22 Feb 2010 16:55:04 +0000</pubDate><guid>https://www.rottenbytes.info/2010/02/22/when-puppet-meets-nginx/</guid><description>&lt;p&gt;&lt;img class="size-full wp-image-252 alignleft" title="Absolut_nginx" src="http://www.rottenbytes.info/wp-content/uploads/2010/02/Absolut_nginx.jpg" alt="Absolut_nginx" width="90" height="250" /&gt;At $WORK I started using Nginx a while ago, first as a front end to my mongrel instances for puppet. Recently I began to use it for one of its most know features : reverse proxy (and caching too). Of course this work had to be puppetized !&lt;/p&gt;</description></item><item><title>Puppet &amp; munin : little things added</title><link>https://www.rottenbytes.info/2009/08/05/puppet-munin-little-things-added/</link><pubDate>Wed, 05 Aug 2009 09:58:35 +0000</pubDate><guid>https://www.rottenbytes.info/2009/08/05/puppet-munin-little-things-added/</guid><description>&lt;p&gt;&lt;img class="alignleft size-thumbnail wp-image-54" title="kermit" src="http://www.rottenbytes.info/wp-content/uploads/2009/01/kermit.jpg" alt="" width="108" height="127" /&gt;Disclaimer : this work is mostly based upon DavidS work, available on &lt;a href="http://git.black.co.at"&gt;his git repo&lt;/a&gt;. In the scope of my work I needed to have munin support for freeBSD &amp;amp; Solaris. I also wrote a class for snmp_plugins &amp;amp; custom plugins. Some things are quite dependant from my infrastructure, like munin.conf generation script but it can easily be adapted to yours, by extracting data from your CMDB.&lt;/p&gt;</description></item><item><title>Munin : p&amp;#8217;tit plugin pour ZFS</title><link>https://www.rottenbytes.info/2009/03/04/munin-ptit-plugin-pour-zfs/</link><pubDate>Wed, 04 Mar 2009 12:34:16 +0000</pubDate><guid>https://www.rottenbytes.info/2009/03/04/munin-ptit-plugin-pour-zfs/</guid><description>&lt;p&gt;&lt;img class="alignleft size-full wp-image-62" title="eth0" src="http://www.rottenbytes.info/wp-content/uploads/2009/02/eth0.jpg" alt="eth0" width="63" height="80" /&gt;Et voila, mon premier plugin pour munin ! C’est un plugin solaris only (utilisation du module Kstat oblige) qui permet de monitorer les I/O sur les pools ZFS. Je n’ai pas trouvé comment faire des stats par pool (comprendre à la “zpool iostat”) et si quelqu’un a une astuce à ce niveau là, je suis preneur. En attendant voici &lt;a rel="attachment wp-att-80" href="http://www.rottenbytes.info/?attachment_id=80"&gt;le fichier&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Enlarge your munin, part 2</title><link>https://www.rottenbytes.info/2009/02/26/enlarge-your-munin-part-2/</link><pubDate>Thu, 26 Feb 2009 10:54:29 +0000</pubDate><guid>https://www.rottenbytes.info/2009/02/26/enlarge-your-munin-part-2/</guid><description>&lt;p&gt;&lt;img class="alignleft size-full wp-image-62" title="eth0" src="http://www.rottenbytes.info/wp-content/uploads/2009/02/eth0.jpg" alt="eth0" width="80" height="103" /&gt;Tips rapide : pour accélerer la collecte des données avec munin-update, ajoutez dans /etc/munin/munin.conf du master :&lt;/p&gt;</description></item><item><title>Enlarge your munin</title><link>https://www.rottenbytes.info/2009/02/25/enlarge-your-munin/</link><pubDate>Wed, 25 Feb 2009 16:10:53 +0000</pubDate><guid>https://www.rottenbytes.info/2009/02/25/enlarge-your-munin/</guid><description>&lt;p&gt;&lt;img class="alignleft size-full wp-image-62" title="eth0" src="http://www.rottenbytes.info/wp-content/uploads/2009/02/eth0.jpg" alt="eth0" width="80" height="103" /&gt;Au boulot j’ai remplacé &lt;a href="http://www.cacti.net"&gt;cacti&lt;/a&gt; par &lt;a href="http://munin.projects.linpro.no/"&gt;munin&lt;/a&gt;. Munin c’est choupi, la conf est en flat file mais ça a deux défauts, ou un selon le point de vue : le &lt;a href="http://munin.projects.linpro.no/wiki/CgiHowto"&gt;munin-cgi-graph&lt;/a&gt; est tout simplement moisi car d’une lenteur sans nom, et générer les images lors du poll c’est long. Sauf quand on tombe sur ce petit &lt;a href="http://blog.apokalyptik.com/2009/01/23/making-munin-graph-take-advantage-of-multiple-cpuscores/"&gt;hack&lt;/a&gt; convivial qui permet de lancer en parallèle la génération pour X nodes. Malheureusement, l’exemple donné en lien n’est valable que pour la version du trunk (au moment ou j’écris ceci) et pas pour la version 1.2.6 livrée avec lenny. J’ai donc modifié mon munin-graph en “portant” le hack disponible. Résultat : 2min30s au lieu de 9min pour la génération de 80 machines (dont certaines avec &lt;strong&gt;beaucoup&lt;/strong&gt; d’infos)&lt;/p&gt;</description></item></channel></rss>