rrd-configuration.properties error in comment

Description

in poller-configuration.xml is written

  1. This property indicates whether we should use this system or not. Is set to true

  2. the queuing system will prioritize non-zero valued updates over zero valued updates.

  3. If it is false then all updates will be counted as significant.
    #

  4. The default setting is 'false' (mark non-zero data as significant and zero as insignificant
    #

  5. Note: A misspelling of the work Significant was discovered and fixed here.. if this is not working

  6. properly for you in make sure you are spelling significant correctly.
    #
    #org.opennms.rrd.queuing.prioritizeSignificantUpdates=false

which is quite a bit confusing... (like don't do while not true winking face

Obviously it should be

  1. The default setting is 'false' (don't mark zero data as insignificant)

Environment

Operating System: All Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Seth Leger February 10, 2011 at 9:44 PM

Fixed in master.

commit 4ae690bbd203acac65f9d88dfaa3ff283492c1ca

Matt Brozowski February 8, 2011 at 5:09 PM

Why haven't we fixed this sooner!!! Thanks guys!

Michael March 12, 2010 at 5:06 AM

The doku error is still there in 1.7.10, but I stated the wrong config file. In veritas it's written in

rrd-configuration.properties

I would now propose to write

  1. The default setting is 'false'

instead of

  1. The default setting is 'false' (mark non-zero data as significant and zero as
    insignificant

Fixed

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

PagerDuty

Created February 5, 2009 at 10:36 AM
Updated January 27, 2017 at 4:26 PM
Resolved February 10, 2011 at 9:44 PM

Flag notifications