[opennms-devel] Re: [opennms-discuss] Alarns based on LAST/MAX rrd value and not AVERAGE

[Wiktor W. <wik...@ne...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 14 December 2004 15:41, David Hustace wrote:
> On Dec 14, 2004, at 7:57 AM, Wiktor Wodecki wrote:
> > A brief look into the sourcecode at rrd/JniRrdStrategy.java:207 shows
> > that the
> > average value is hardcoded into the rrdtool query. Is there another
> > way than
> > to recode the method to achieve the goal of avoiding an average match?
=2E..
> As far as configuration goes, we can use a constant maintained in the
> rrd-configuration.properties file (this would be a global change) or we
> can change the thresholding-config.xsd to accept the RRA as a
> attribute.  Neither should be very difficult.  As always, I would
> suggest openning an enhancement bug in http://bugzilla.opennms.org.

I wrote a preliminary patch which extends the fetchLastValue with an acctyp=
e=20
string and compile tested it. However I somehow cannot make opennms recogni=
ze=20
the added attribute in thresholds.xml for one entry. I think that I missed=
=20
something in the mapping between the thresholding-config.xsd and the=20
ThresholdingConfigFactory but I cannot find the error. Could you please=20
provide some insight how variables are interpreted from an xml file in=20
opennms?
I attached my patch so you can look how I did it (for now I concentrated on=
=20
JniRrdStrategy and didn't care too much about the others beside that they=20
must compile)

Thanks for the help,

=2D --=20
Regards,
=20
 Wiktor Wodecki
   =20
 net mobile AG - 40470 Duesseldorf - Germany
 923B DCF8 070C 9FDD 5E05  9AE3 E923 5A35 182C 9783

=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBvx9m6SNaNRgsl4MRAmLlAJoCBo5+WCXHUdJgotyExkNlyHEpJACgwQZV
4zIO/Uv8ZkZ6VwBNIEUBffM=3D
=3DLpIf
=2D----END PGP SIGNATURE-----