Nodata triggers immediately fire on newly created hosts

XMLWordPrintable

    • Type: Incident report
    • Resolution: Fixed
    • Priority: Major
    • 2.1.5
    • Affects Version/s: 1.8.9, 1.9.8 (beta), 2.0.6
    • Component/s: Server (S)

      Steps to reproduce:

      • Create a template with some item and a nodata trigger on it
      • Create a new host and apply the template

      If you're not lucky to get data for that item in the first couple of seconds the nodata trigger will fire.

      Expected behaviour:

      • Only fire after the nodata timeout is reached

      I tried to work around this kind of problem by extending the trigger expression with something like "... & {bla:min(#1)}" (can't remember right now).

      This bug is somewhat related to ZBX-4256, which you can easily reproduce, contrary to what is the closing reason. Just in case you consider disabling a host bad practice, why is it there in the first place?

            Assignee:
            Unassigned
            Reporter:
            Volker Fröhlich
            Votes:
            11 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: