Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-13208

Preprocessing is not applied to first value of new item

XMLWordPrintable

    • Team A
    • Sprint 23, Sprint 25
    • 1

      We have a LLD with several item prototypes, some of which have preprocessing steps configured. In particular, for two item prototypes we have a single step configured consisting of a custom multiplier. Now, when a new actual item is created from either of these prototypes, we noticed that the first (and only the first) value stored is the raw value without preprocessing - all subsequent values, however, have the custom multiplier correctly applied. This is causing a number of spurious triggers and alerts in our setup.

      To recap, the following should be sufficient to reproduce it:

      1. Create a LLD
      2. Create an Item Prototype, of type Numeric, and configure it with a single preprocessing step consisting of a custom multiplier
      3. wait for an item to be created and a few values to be stored
      4. look at the values and notice that the first one does not have the custom multiplier applied to it, but the rest do

        1. Screenshot_1.png
          Screenshot_1.png
          30 kB
        2. Screenshot_2.png
          Screenshot_2.png
          11 kB
        3. Screenshot_3.png
          Screenshot_3.png
          25 kB
        4. DiscoveryRule.png
          DiscoveryRule.png
          32 kB
        5. DiscoveryRuleFilter.png
          DiscoveryRuleFilter.png
          19 kB
        6. ItemDefinition.png
          ItemDefinition.png
          39 kB
        7. ItemDefinitionPreprocessing.png
          ItemDefinitionPreprocessing.png
          16 kB
        8. ReportedValues.png
          ReportedValues.png
          42 kB

            vso Vladislavs Sokurenko
            roadrunner A B
            Team A
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: