[NZLUG] monitoring software.

Martin D Kealey martin at kurahaupo.gen.nz
Thu Jul 21 12:50:12 NZST 2016

On the list of things to do I'd also recommend using additional IP addresses
for different functions, so that you can migrate some or all to different
hosts in the future without having to reconfigure all the devices that
depend on them.

(The term "VIP" is apposite, but people tend to associate that with load
balancing, which is most definitely *not* what I'm talking about.)

With, of course, separate DNS entries -- though it's arguable whether DNS
should be used for monitoring; there are benefits and problems both ways.

You might also take the opportunity to enable IPv6 on your monitoring system
so that it can cope as IPv6 is added to other parts of the network later.


On Thu, 21 Jul 2016, steve wrote:

> Date: Thu, 21 Jul 2016 12:01:02
> From: steve <steve at greengecko.co.nz>
> Reply-To: NZ Linux Users Group <nzlug at lists.nzoss.org.nz>
> To: nzlug at lists.nzoss.org.nz
> Subject: Re: [NZLUG] monitoring software.
> This is interesting. I've spun up a local VM to try out a few things.
> Zabbix was first on my list, but with a (Norwegian) nul points so far,
> I'll try Icinga2 instead!.
> I'll also look into that addon, thanks Jim.
> Steve
> On 07/21/2016 10:56 AM, Jim Cheetham wrote:
> > Use nagios with check_mk - all your config concerns go away, all the
> > tests are done at the far end rather than from the nagios server, etc.
> > That's more important than the GUI gloss, which is usually all the
> > other products really produce.
> >
> > -jim
> > _______________________________________________
> > NZLUG mailing list
> > NZLUG at lists.nzoss.org.nz
> > http://lists.nzoss.org.nz/mailman/listinfo/nzlug
> >

More information about the NZLUG mailing list