-
Type:
Problem report
-
Resolution: Unresolved
-
Priority:
Critical
-
Affects Version/s: 7.0.25
-
Component/s: Server (S)
-
None
-
Environment:Zabbix 7.0.25/MySQL
-
S26-W18/19, S26-W20/21, S26-W22/23
-
1
Steps to reproduce:
- Create item which will be not supported and have schedule interval like m0-59 and main update interval set to 0
- Make trigger with this item with nodata(30m)
- Enable internal action for this
Result:
Expected:
Do not flood events/problems, this further makes extensive workload for housekeeper, especially on large instance, which basically causes same "fixed" issue with deadlock on the event_recovery/events: https://support.zabbix.com/browse/ZBX-16925 due to high amount of such not supported items.
- caused by
-
ZBX-22580 Nodata triggers after proxy becomes available
-
- Closed
-
- related to
-
ZBXNEXT-10636 Update nodata() trigger to never move into UNKNOWN state (unless it was misconfigured)
-
- Open
-