<story><title>Stop using Nagios (so it can die peacefully)</title><url>http://www.slideshare.net/superdupersheep/stop-using-nagios-so-it-can-die-peacefully</url></story><parent_chain><item><author>seiji</author><text>You&amp;#x27;re presenting the MySQL argument.  &amp;quot;Why should we switch since we know it fails in exactly these 1,000 different ways and we can fix these problems?  Using something better has unknown failure scenarios!&amp;quot;&lt;p&gt;Have you ever been woken up by a nagios page that automatically cleared after five minutes because the incoming queue was delayed past the alert interval?&lt;p&gt;Have you ever had your browser crash because you click on the wrong thing in the designed-in-1996-and-never-updated nagios interface and had your browser crash because it dumps 500MB of logs to your screen?&lt;p&gt;Have you ever had services wake you up with alert then clear then alert then clear again because some new intern configured a new monitor but didn&amp;#x27;t set up alerting correctly (because lol, they don&amp;#x27;t get paged, so who gives a flip if they copied and pasted the wrong template config, as is standard practice)?&lt;p&gt;Have you had to hire &amp;quot;nagios consultants&amp;quot; to figure out how to scale out your busted monitoring infrastructure because nagios was designed to run on a single core Pentium 90?&lt;p&gt;Being pro-nagios is like being pro-Russia, pro-North Korea, and pro-Rap Genius while arguing &amp;quot;but at least we know how bad they are and can keep them in line.&amp;quot;</text></item><item><author>markdennehy</author><text>So... stop using a debugged and stable tool whose limitations and problems are well-known and understood and replace it with six bits of software duct-taped together, two of which aren&amp;#x27;t working yet (if they even exist), without any idea of how they interact when they hit edge cases.&lt;p&gt;I mean, &amp;quot;don&amp;#x27;t use X, use ShinyX instead&amp;quot; is one thing (and most of the time it&amp;#x27;s a bad thing but it does occasionally turn up good ideas), but this is just So Much Worse...</text></item></parent_chain><comment><author>madaxe_again</author><text>Did you &lt;i&gt;seriously&lt;/i&gt; just equate North Korea, Russia, Rap Genius and Nagios?&lt;p&gt;Everyone knows that Rap Genius is an oppressive regime in which you&amp;#x27;re executed for dissent, North Korea are SEO spammers, and in Russia... there is no need for monitoring software because &lt;i&gt;Russian computer does not fail!&lt;/i&gt;</text></comment>
<story><title>Stop using Nagios (so it can die peacefully)</title><url>http://www.slideshare.net/superdupersheep/stop-using-nagios-so-it-can-die-peacefully</url></story><parent_chain><item><author>seiji</author><text>You&amp;#x27;re presenting the MySQL argument.  &amp;quot;Why should we switch since we know it fails in exactly these 1,000 different ways and we can fix these problems?  Using something better has unknown failure scenarios!&amp;quot;&lt;p&gt;Have you ever been woken up by a nagios page that automatically cleared after five minutes because the incoming queue was delayed past the alert interval?&lt;p&gt;Have you ever had your browser crash because you click on the wrong thing in the designed-in-1996-and-never-updated nagios interface and had your browser crash because it dumps 500MB of logs to your screen?&lt;p&gt;Have you ever had services wake you up with alert then clear then alert then clear again because some new intern configured a new monitor but didn&amp;#x27;t set up alerting correctly (because lol, they don&amp;#x27;t get paged, so who gives a flip if they copied and pasted the wrong template config, as is standard practice)?&lt;p&gt;Have you had to hire &amp;quot;nagios consultants&amp;quot; to figure out how to scale out your busted monitoring infrastructure because nagios was designed to run on a single core Pentium 90?&lt;p&gt;Being pro-nagios is like being pro-Russia, pro-North Korea, and pro-Rap Genius while arguing &amp;quot;but at least we know how bad they are and can keep them in line.&amp;quot;</text></item><item><author>markdennehy</author><text>So... stop using a debugged and stable tool whose limitations and problems are well-known and understood and replace it with six bits of software duct-taped together, two of which aren&amp;#x27;t working yet (if they even exist), without any idea of how they interact when they hit edge cases.&lt;p&gt;I mean, &amp;quot;don&amp;#x27;t use X, use ShinyX instead&amp;quot; is one thing (and most of the time it&amp;#x27;s a bad thing but it does occasionally turn up good ideas), but this is just So Much Worse...</text></item></parent_chain><comment><author>volume</author><text>I think his point is there are tradeoffs, and I agree. On top of that, meaningful debate over what tool should be about what context you&amp;#x27;re in. This applies to the OP&amp;#x27;s slidedeck.&lt;p&gt;To give context about my comment about context:&lt;p&gt;* was nagios setup before you started the job?&lt;p&gt;* did you setup nagios yourself?&lt;p&gt;* is your internal process for managing nagios broken?&lt;p&gt;* culturally do you work at a place where ops is an afterthought?&lt;p&gt;* if Nagios is your technical debt do you have a way out? are you crushed by other commitments? Maybe it&amp;#x27;s more of a management&amp;#x2F;culture issue.&lt;p&gt;... hmm actually I should stop. From re-reading your comment, I can&amp;#x27;t tell how much of it is trolling (in a entertaining Skip Bayless, right wing radio, Jim Cramer kind of way).</text></comment>