-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Ref http://issues.opennms.org/browse/NMS-4244, I have found something
interesting: Thresholding is attempted even if the data collection cycle failed.
Any missing values will not be thresholded, except for counter values, which
it'll try to do anyway based on the last value, hence the bug report.
My question:
Can anyone see a reason why moving thresholding to only occur if the
collection
succeeded (see CollectableService.doCollection())?
My concern is that we might currently have situations where the data collection
partly succeeds (e.g. some OIDs are returned but not others). Currently
thresholding will work for the values are have managed to be collected; changing
this as suggested means it'll never threshold in the presence of any error on
that collection cycle (per node/collector).
Before I spend a few days in the bowels of the collectors, does anyone know if
I'm worried about something that can even happen (partial collection result
sets)?
Ta,
- --
Craig Miskell
Senior Systems Administrator
Opus International Consultants
Phone: +64 4 471 7209
73 is the Chuck Norris of Numbers
-Leonard, on The Big Bang Theory
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAk23NNAACgkQmDveRtxWqnZSQQCghqa/wKZFOJeKv1q5XJLC1z/m
focAn3iC/mhMqNSaHTDS14s7rcS1UcWQ
=MOEi
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
