<div dir="ltr">The newer stuff offers lots of HA options, some are NAgios config compatible, most are nagios test compatible. The biggest win is the additional flexibility, the ability to more easily add and remove nodes or tests from the config, and the much simpler configs themselves. They are just much more well suited for environments where things change. Most of these tools are not nearly as mature as Nagios, so I think Nagios has plenty of runway as a viable monitoring platform, but unless it evolves in a major way, I think we're all going to be saying "remember Nagios? I used to...." in no more than 10 years time. </div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 10, 2015 at 9:50 AM, Dan Kulinski <span dir="ltr"><<a href="mailto:daniel@kulinski.net" target="_blank">daniel@kulinski.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Quentin,<div><br></div><div>Nagios has such a rich support community and a bunch of premade scripts to alert on a wide variety of network software. Are the newer alerting/monitoring packages creating compatibility to migrate these scripts to their new environment? Beyond these basic scripts, do these new packages offer items such as high availability monitoring out of the box? (Nagios can be a pain to set up in this fashion). We use Nagios widely and to switch would most likely be a major endeavor, but it is something I wouldn't mind looking into.</div><div><br></div><div>Thanks,</div><div> Dan Kulinski</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 10, 2015 at 9:43 AM, Quentin Hartman <span dir="ltr"><<a href="mailto:qhartman@gmail.com" target="_blank">qhartman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">While you're messing around with Nagios, it would probably be worth spending some time messing around with Sensu or some other more modern alerting systems. NAgios is definitely the old standard for OSS alerting, but there is a new generation of tools out there (Sensu among them) that are likely to start supplanting it in a major way in the not too distant future. The biggest reason for that is that they work better in more elastic environments than Nagios does. Once I have some time to work on it, I intend to replace all of my alerting installations that are currently running Nagios with Sensu.<span><font color="#888888"><div><br></div><div>QH</div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 10, 2015 at 9:14 AM, <span dir="ltr"><<a href="mailto:foo7775@comcast.net" target="_blank">foo7775@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Arial;font-size:12pt;color:#000000"><div>Heh - thanks Dennis, but you may be giving me too much credit. And Mike probably has more expertise in the subject - he definitely has "seniority"! ;-) <em>(Although I *have* been thinking about documenting the process so that my nephew could follow along, so I guess that using the documentation as the basis for a talk isn't too much of a stretch from that...)</em><br></div><div><br></div><div>My rationale for the project is simply that I've wanted to mess around with Nagios for a while now, plus the aforementioned need to keep an eye on the components on that segment. Combine that with the fact that I don't have a separate computer to place on this segment (& a "full computer" would pretty much be overkill anyway) & the creation of what is (effectively) a single-purpose "appliance" is an easy decision to make.<br></div><div><br></div><div>I guess if there's enough interest, I could think about giving a talk to the group.<br></div><div><br></div><hr><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From: </b><a href="mailto:dennisjperkins@comcast.net" target="_blank">dennisjperkins@comcast.net</a><span><br><b>To: </b>"CLUE's mailing list" <<a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a>><br></span><b>Sent: </b>Wednesday, June 10, 2015 7:54:18 AM<br><b>Subject: </b>Re: [clue] LAMP + Nagios on Pi?<div><div><br><div><br></div><div style="font-family:Arial;font-size:12pt;color:#000000"><div>I haven't used Nagios but this sounds interesting. Maybe you could give a talk about it after you get it working.<br></div><div><br></div><div><br></div><hr><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From: </b><a href="mailto:foo7775@comcast.net" target="_blank">foo7775@comcast.net</a><br><b>To: </b>"CLUE list" <<a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a>><br><b>Sent: </b>Tuesday, June 9, 2015 11:14:42 PM<br><b>Subject: </b>[clue] LAMP + Nagios on Pi?<br><div><br></div><div style="font-family:Arial;font-size:12pt;color:#000000"><div>Hey guys (& gals),<br></div><div><br></div><div> I'm giving serious thought to setting up a "latest generation" Raspberry Pi as a headless server running Nagios so that I can quickly & easily check up on one segment of my home network when/if the mood strikes me. Has anyone on this list set up Nagios on a Pi system, & if so, do you have any suggestions, or any "gotchas" to watch out for?? (Aside from the obvious ARM architecture as opposed to x86/64...)<br></div><div><br></div><div> It may be worth noting that I will be setting it up to boot RedSleeve (RHEL-derived) instead of the Debian-derived OS that it comes with...<br></div><div><br></div><div>Thanks in advance,<br></div><div><br></div><div>T.<br></div></div><br>_______________________________________________<br>clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>For information, account preferences, or to unsubscribe see:<br><a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a></div><div><br></div></div><br>_______________________________________________<br>clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>For information, account preferences, or to unsubscribe see:<br><a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a></div></div></div><div><br></div></div></div><br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>