[195332] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Zabbix IT Services feature set

daemon@ATHENA.MIT.EDU (valdis.kletnieks@vt.edu)
Tue Jul 18 12:13:14 2017

X-Original-To: nanog@nanog.org
From: valdis.kletnieks@vt.edu
X-Google-Original-From: Valdis.Kletnieks@vt.edu
To: Graham Johnston <johnstong@westmancom.com>
In-Reply-To: <82C0CE81789FE64D8F4D1526319182972F8CA724@MSG6.westman.int>
Date: Tue, 18 Jul 2017 12:13:03 -0400
Cc: "'nanog@nanog.org'" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

--==_Exmh_1500394383_2924P
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, 18 Jul 2017 14:33:19 -0000, Graham Johnston said:
> My question is, has anyone gotten the Zabbix IT Services to work correc=
tly? =A0
> Is there a trick to getting it to work, some configuration we are doing=
 incorrectly?

We're a Zabbix shop, with a large number of boxes being monitored.

This may or may not be your problem, but it bit me big time when were wer=
e
first getting it up and running.  There's a =22gotcha=22 with triggers, i=
n that
they may have *TWO* values to provide hysteresis.  So if you have a trigg=
er set
to go off at 25 wombats/second, and your system hits 32 wps, the trigger =
will
flag a problem.  It will *continue* doing so *not* until it drops below
25 wps, but until it drops down to the =22clear=22 value (for example 10 =
wombats/sec).
SO you can be sitting at 11 or 13 or 12 for a long time, but it won't go
to OK until till it's below 10 when Zabbix checks. (A side effect is if i=
t
manages to have a very short dip to 9.8 wps, and back up to 13, you'll be=

scratching your head wondering how it went to OK. :)

(And then of course there's the =22somebody had a wild hair=22 cases wher=
e the
trigger into trouble state is one hand-coded expression checking one thin=
g, and
the =22OK=22 trigger checks something entirely different. :)

Hope that helps.

--==_Exmh_1500394383_2924P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Comment: Exmh version 2.8.0 04/21/2017

iQEVAwUBWW4zj40DS38y7CIcAQJYyggAsmUXC3Rhftq5oTjjk7ekBCpbCgqTfl3U
ouLO0fekeyyZTaLEUoDFjPV7a0QOU4UYIsKX5UVYxdznajAUz2gxHPVJ12MZwUdo
T7kJVVyiWuMuZugC+gfXFX+XGJyioCzWn/SvCVMCW+pyMnsBXEDrUT7wKqSgoeOc
nXyxmjFfHnhu8FViAG3Bq1GlKNJXbJkoI9dgtH22L2vYapRx2TBIQ9QSkMeyBiOS
kpq2Pnm5xBCYBglA8NOLxFb34LQ1kLojLTFhGFUnyzAFN0Ml/9LIObiYnm+BYC++
2s9h4UYHiPBOz0qie1OorcLMVWAINIOAXXqFVxHjsu6IAWQ3MOEmmQ==
=Nn4G
-----END PGP SIGNATURE-----

--==_Exmh_1500394383_2924P--

home help back first fref pref prev next nref lref last post