[clue] LAMP + Nagios on Pi?

[Quentin Hartman]

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.

On Wed, Jun 10, 2015 at 9:50 AM, Dan Kulinski <daniel at kulinski.net> wrote:

> Quentin,
>
> 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.
>
> Thanks,
>   Dan Kulinski
>
> On Wed, Jun 10, 2015 at 9:43 AM, Quentin Hartman <qhartman at gmail.com>
> wrote:
>
>> 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.
>>
>> QH
>>
>> On Wed, Jun 10, 2015 at 9:14 AM, <foo7775 at comcast.net> wrote:
>>
>>> 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"!  ;-)   *(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...)*
>>>
>>> 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.
>>>
>>> I guess if there's enough interest, I could think about giving a talk to
>>> the group.
>>>
>>> ------------------------------
>>> *From: *dennisjperkins at comcast.net
>>> *To: *"CLUE's mailing list" <clue at cluedenver.org>
>>> *Sent: *Wednesday, June 10, 2015 7:54:18 AM
>>> *Subject: *Re: [clue] LAMP + Nagios on Pi?
>>>
>>>
>>> I haven't used Nagios but this sounds interesting.  Maybe you could give
>>> a talk about it after you get it working.
>>>
>>>
>>> ------------------------------
>>> *From: *foo7775 at comcast.net
>>> *To: *"CLUE list" <clue at cluedenver.org>
>>> *Sent: *Tuesday, June 9, 2015 11:14:42 PM
>>> *Subject: *[clue] LAMP + Nagios on Pi?
>>>
>>> Hey guys (& gals),
>>>
>>>   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...)
>>>
>>>   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...
>>>
>>> Thanks in advance,
>>>
>>> T.
>>>
>>> _______________________________________________
>>> clue mailing list: clue at cluedenver.org
>>> For information, account preferences, or to unsubscribe see:
>>> http://cluedenver.org/mailman/listinfo/clue
>>>
>>>
>>> _______________________________________________
>>> clue mailing list: clue at cluedenver.org
>>> For information, account preferences, or to unsubscribe see:
>>> http://cluedenver.org/mailman/listinfo/clue
>>>
>>>
>>> _______________________________________________
>>> clue mailing list: clue at cluedenver.org
>>> For information, account preferences, or to unsubscribe see:
>>> http://cluedenver.org/mailman/listinfo/clue
>>>
>>
>>
>> _______________________________________________
>> clue mailing list: clue at cluedenver.org
>> For information, account preferences, or to unsubscribe see:
>> http://cluedenver.org/mailman/listinfo/clue
>>
>
>
> _______________________________________________
> clue mailing list: clue at cluedenver.org
> For information, account preferences, or to unsubscribe see:
> http://cluedenver.org/mailman/listinfo/clue
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cluedenver.org/pipermail/clue/attachments/20150610/4eae788e/attachment.html