From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: monit and friends.
Date: Mon, 16 Oct 2017 18:18:18 +0200 [thread overview]
Message-ID: <b121cf27-d55a-2c85-586b-cc5ce2705c5f@gmail.com> (raw)
In-Reply-To: <c636b736-1d48-ee25-f62c-333d9722c3c1@monksofcool.net>
On 16/10/2017 18:10, Ralph Seichter wrote:
> On 16.10.2017 17:50, Alan McKinnon wrote:
>
>> Nagios and I go way back, way way waaaaaay back. I now recommend it
>> never be used unless there really is no other option.
>
> Have you tried Icinga 2 (*) yet? It originally started as a Nagios fork
> and uses plugins to monitor, but the rule-based configuration mechanism
> of Icinga 2 is IMO more powerful and easier than Nagios' mechanism. I've
> used both Nagios and Icinga for years, and I definitely prefer Icinga 2.
>
> -Ralph
>
> (*) https://www.icinga.com/products/icinga-2/
>
Yes, I know Icinga as well. It fixes many of Nagios' shortcomings - the
first batch of commits after the fork took care of many of those - but
still suffers from all of Nagios' design faults.
In short, I'm not interested in going back to Nagios after a year's
migration to get away from it. Same for Icinga, Shinken, Sensu and all
the other many nagios forks out there. Also Zabbix.
My current monitoring is snmp-based, and all I need monit for is as a
very narrowly-defined single-purpose watchdog.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2017-10-16 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 12:11 [gentoo-user] monit and friends Alan McKinnon
2017-10-16 15:08 ` [gentoo-user] " Ian Zimmerman
2017-10-16 15:12 ` Alan McKinnon
2017-10-16 15:41 ` Mick
2017-10-16 15:50 ` Alan McKinnon
2017-10-16 16:10 ` Ralph Seichter
2017-10-16 16:18 ` Alan McKinnon [this message]
2017-10-17 0:13 ` Michael Orlitzky
2017-10-18 13:45 ` skyclan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b121cf27-d55a-2c85-586b-cc5ce2705c5f@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox