[erlang-questions] app for watching/monitoring other erlang nodes

Garrett Smith g@REDACTED
Wed Nov 21 00:55:48 CET 2012

On Tue, Nov 20, 2012 at 5:37 PM, Loïc Hoguin <essen@REDACTED> wrote:
> On 11/20/2012 07:43 PM, Zabrane Mickael wrote:
>>> I've spent a lot of time dealing with Nagios quality issues, and
>>> eventually decided to never use it again. If I knew that ahead of time
>>> I could have skipped all that. So yeah, risk.
>> Still can't understand why people spent time using bad designed softwares.
>> No serious person uses Nagios these days.
> Pretentious much?
> I don't use it, but I know many people who do, for the simple reason that it
> works for them. Why change what's not broken, etc. If it doesn't work for
> you, sure, but don't diss out people who don't have issues with using it.
> Let me send you back your comment modified: No serious person asks
> themselves "is it well designed?" instead of "does it work?" as their most
> important criteria to choosing which software to use. Can do the same about
> changing software that works.

Everyone's entitled to lash out emotionally at a software package
that's caused them pain :)

I do think this is an excellent application for Erlang though. Even
really stupid, naive code can live very well in production
environments. You want to monitor something, create a process that
just repeats mindlessly checking. Supervise it. You can easily have
10K of these things and they'll just work, probably.

If a check fails, the process sends uses a REST call for one of a
dozen great email services or SMS gateways to notify someone. Maybe
write to a dets table that's served via a simple http interface
(Cowboy!) to provide a simple workflow for problem resolution.

Fun stuff!

And no, we shouldn't bash Nagios. It's hardly sporting.


More information about the erlang-questions mailing list