[BBLISA] Monitoring survey

Antony Rudie antony.rudie at gmail.com
Thu Feb 4 08:38:29 EST 2016


That last sentence is god's own truth.

One more thing you need:  A solid plan for what happens to the alerts.
Where do they go?  who deals with them?  How do you know if they've been
dealt with?  It's not rocket science, but it's really important.  I worked
in a place where that piece was missing, and frankly, I'm not sure the
whole monitoring setup added any value.

On Wed, Feb 3, 2016 at 7:52 PM, John Stoffel <john at stoffel.org> wrote:

>
> One of the things that people seem to miss, or overlook in my opinion
> is the cost of doing all this monitoring, and the steep learning curve
> you have for all of it.  It's going to suck in a bunch of time at
> first, way more than people think, and getting it tuned so that it's
> not sending out false alarms is a huge task.
>
> I've played with Nagios, and we have Solarwinds at $WORK, but neither
> is well done or really used outside of silos.  I also played around
> with collectd and graphite, but found it too simplistic in terms of
> access control for what I/we wanted.  And we have an old instance of
> WhatsUp running as well for another group.  It's all hodge podge.  We
> really should dedicate someone to doing this work, but we all keep
> getting pulled in new directions all the time.
>
> It might be easier if you're just upgrading from something and you
> know what you want to monitor, etc.  But it's not a simple drop-in
> tool like some people make out.  It requires commitment and discipline
> to use effectively.
>
> John
>
> _______________________________________________
> bblisa mailing list
> bblisa at bblisa.org
> http://www.bblisa.org/mailman/listinfo/bblisa
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.bblisa.org/pipermail/bblisa/attachments/20160204/f321a82c/attachment.html>


More information about the bblisa mailing list