Change per second preprocessing gives great difference when values received shorter then in one second

XMLWordPrintable

    • Type: Problem report
    • Resolution: Cannot Reproduce
    • Priority: Trivial
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      Happens that trapper items receive more values then expected.

      Received values in 100 ms or less after preprocessing gives enormous results.

      It is unable to predict and adjust trigger thresholds for that.

      Formula: (valueprev_value)/(timeprev_time)

      Example for 1 second interval:

      (100-95)/1 = 5

      Example for 100ms interval:

      (100-95)/0.1 = 50

      Example for 10 ms interval:

      (100-95)/0.01 = 500

       

       

            Assignee:
            Unassigned
            Reporter:
            Andrey Tocko (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: