I just updated our Zabbix server from v5 to v6 and all went pretty smoothly. One of the problems I'm running into post-upgrade are the triggers we use to monitor Elastic Search. We have use template called "Template_CPE_Registry_status", and that template has 3 triggers. All three of these triggers use the same "Item" named "CPE_Registry_status", type "Zabbix Agent" and with a key value of "registry_status".
All 3 triggers are the same except for the text in the search. Here's an example...
Trigger name: "Global Registry service is not available"
This was all working just fine under Zabbix 5. As soon as I upgraded to Zabbix 6 all of these alerts went off saying "Global Registry service is not available".
Obviously, I'm being tripped up by one of the many new changes in Zabbix 6. Any thoughts?
All 3 triggers are the same except for the text in the search. Here's an example...
Trigger name: "Global Registry service is not available"
Code:
find(/Template_CPE_Registry_status/registry_status,,"regexp","\\\"Global CPE Registry Service \\\":\\\"Is Available\\\"")=0
Obviously, I'm being tripped up by one of the many new changes in Zabbix 6. Any thoughts?
Comment