-
Incident report
-
Resolution: Fixed
-
Major
-
1.8.9, 1.9.8 (beta), 2.0.6
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?
- is duplicated by
-
ZBX-6134 Trigger included nodata func is evaluated as Failed at the first time.
- Closed
-
ZBX-6691 False nodata() triggering for a historyless log item, which status was manually changed from "Not supported" to "Enabled"
- Closed
-
ZBX-6767 Host set into state "not monitored" still send alert notifications
- Closed