From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] open source monitoring on gentoo
Date: Mon, 27 Jun 2011 19:52:11 +0200 [thread overview]
Message-ID: <1451410.TNjbug7ugX@nazgul> (raw)
In-Reply-To: <201106271733.56000.michaelkintzios@gmail.com>
On Monday 27 June 2011 17:33:45 Mick did opine thusly:
> On Monday 27 Jun 2011 08:45:06 Stefan G. Weichinger wrote:
> > thanks to all for your suggestion.
> > Still not sure where to turn ...
> >
> > Stefan
>
> We can't know which one may best match your
> needs/expectations/preferences. You can spend some time looking at
> their documentation to get an understanding of how difficult it may
> be to configure them and then play with their online demos to
> experience the touch & feel of each.
>
> Then install the one that best matches your requirements and if your
> don't like it enough install the second best and so on. If you are
> prepared to get your hands dirty you can somewhat customise the
> look and feel (e.g. using CSS), but the monitoring engine is what
> will provide you with the necessary functionality.
>
> Personally, I ended up using Nagios because at the time it had a
> load of plugins that others did not. Once I spent a lot of time
> installing graphing engines and configuring it, I had invested too
> much time to ditch it and try something different.
>
> Thankfully, you can start afresh your quest and evaluate how each of
> these tools meets your requirements.
We're going through the same research nightmare. Our conclusions:
1. Nothing out there just does everything a large network would really
want.
2. Some projects have very stable code but not much plugins, others
have lots of plugins but the dev model leads to unstable code
3. Monitoring is NOT off the shelf, it is highly bespoke
4. Regardless of what you choose you will go through X effort to get
it going and Y effort to get it to do what you want. The value is Y is
amazingly similar regardless of the project (given that the starting
code is at least somewhat mature).
iow, your comments are right on the money, that is indeed how to do
it.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-06-27 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 9:15 [gentoo-user] open source monitoring on gentoo Stefan G. Weichinger
2011-06-24 13:52 ` Mick
2011-06-24 20:05 ` [gentoo-user] " James
2011-06-24 21:45 ` [gentoo-user] " Petric Frank
2011-06-27 7:45 ` Stefan G. Weichinger
2011-06-27 16:33 ` Mick
2011-06-27 16:55 ` 4k3nd0
2011-06-27 17:52 ` Alan McKinnon [this message]
2011-06-29 14:47 ` [gentoo-user] " James
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=1451410.TNjbug7ugX@nazgul \
--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