-
Incident report
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
Sprint 14
IT services use triggerid for binding trigger to a specific service. After updating a template (with updated triggers) through Zabbix API seems like trigger id change its value and IT service stop working.
Zabbix API options for triggers are set to:
- createMissing: true
- updateExisting: true
- deleteMissing: true
Is this an expected behavior or a bug?
Zabbix server version: 3.2.3
OS version : CentOS 7.2
- depends on
-
ZBXNEXT-4001 Introduce unique keys for Items and Triggers
- Closed