From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: monit and friends.
Date: Mon, 16 Oct 2017 16:41:42 +0100 [thread overview]
Message-ID: <6623947.tej94tQTD2@dell_xps> (raw)
In-Reply-To: <e417e7dd-c20d-a389-dfc4-0981f9a3c03c@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2094 bytes --]
On Monday, 16 October 2017 16:12:53 BST Alan McKinnon wrote:
> On 16/10/2017 17:08, Ian Zimmerman wrote:
> > On 2017-10-16 14:11, Alan McKinnon wrote:
> >> My needs here are pretty simple:
> >> local watchdog that checks if a program is running and restart it if
> >> not. If that fails 3 times or so, alert me.
> >> Maybe a few file/dir/fifo monitors as well. Not much else.
> >>
> >> I don't need any of monit's graphing features or M/monit, I have other
> >> tools for that. And mostly don't even need it's http API either.
> >
> > supervisor (aka supervisord)
> >
> > http://supervisord.org/
> >
> > python based, not sure if that's okay with you
>
> I forgot about supervisord. Like monit, it runs everywhere and might be
> easier for the team-mates to understand and work with.
>
> Python is not a problem, all these hosts are ansible-managed anyway, so
> they all have to run python-2.7
>
> Good find, thanks!
I've used Nagios in the past, but have not kept up with its development and
the many plugins it provides. It could do any of the above tasks and much
more. It can run scripts (perl, or bash) via daemons (nrpe) on the remote
systems to restart applications, et al. The Nagios server possessed the
ability to set up quite intelligent monitoring and alert hierarchies with
multilayered comms structures to make sure you are not woken up at 2 a.m. by
your boss, just because a ping failed to his home NAS. I also found the logs
which can be also stored on SQL quite useful both in troubleshooting problems
and in producing reports. It can monitor network connectivity, remote OS
parameters and applications. Writing your own plugin/module to monitor quite
specialised use cases is not particularly difficult either.
I expect you may find Nagios more complicated to set up than monit, at least
initially, but if you don't have the luxury of time to invest on setting up
Nagios monit may be a better fit. I don't have in depth experience with other
monitoring software to comment, so something else may suit better your
specific needs.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-16 15:41 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 [this message]
2017-10-16 15:50 ` Alan McKinnon
2017-10-16 16:10 ` Ralph Seichter
2017-10-16 16:18 ` Alan McKinnon
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=6623947.tej94tQTD2@dell_xps \
--to=michaelkintzios@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