Score:0

Zabbix 6 : Elastic Search Trigger Expression no longer working

br flag

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 a custom template created for one of our internal apps (called "Template_CPE_Registry_status"), and that template has 3 triggers. All three of these triggers use the same "Item" named "CPE_Registry_status", 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

find(/Template_CPE_Registry_status/registry_status,,"regexp","\\\"Global CPE Registry Service \\\":\\\"Is Available\\\"")=0

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?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.