Gang: During Dev-Jam I believe it was, the snmp-graph.properties file was changed to use the MIN/MAX values stored in the RRD file instead of the minimum and maximum of the AVERAGE number. It was a lot of work and I can see some reasoning behind it, but I want to proposed that it be backed out.
By default OpenNMS stores the MIN and MAX daily values. So if I am looking at a subset of the day on a graph, I get the MIN and MAX for the whole day instead of the range I've selected. Try it, zoom in on a 24 hour graph and choose a local maximum and you'll see the value reported is wrong. Plus it takes a day on the new system before those values are other than NaN. It will be a lot of work to back out, as it was a lot of work to create, so I don't want to attempt this unless we are in agreement it should be done. Comments? -T _______________________________________________________________________ Tarus Balog, OpenNMS Maintainer Main: +1 919 533 0160 The OpenNMS Group, Inc. Fax: +1 503 961 7746 Email: [EMAIL PROTECTED] URL: http://www.opennms.org PGP Key Fingerprint: 8945 8521 9771 FEC9 5481 512B FECA 11D2 FD82 B45C ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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