Zabbix intergration

[drifter104]

I've recently migrated from Zabbix 2.4 to Zabbix 3.2.3, this was also a server migration as the previous server had failed. I had a copy of the database though. The previous server used to send alerts to my alerting provider OPSGenie. It done this with an integration via Marid and an action on Zabbix that would call a custom script on the Zabbix server to send the alert.

This part works when called manually, in that I can use the following command

 /etc/opsgenie/zabbix2opsgenie -triggerName='zabbix test alert' -triggerStatus='PROBLEM'

I can see this written to the log file and the provider

/var/log/opsgenie/zabbix2opsgenie.log

When I created the action within Zabbix with the action to call a custom script on the zabbix server with the action.

/etc/opsgenie/zabbix2opsgenie -triggerName="{TRIGGER.NAME}" -triggerId="{TRIGGER.ID}" -triggerStatus="{TRIGGER.STATUS}" -triggerSeverity="{TRIGGER.SEVERITY}" -triggerDescription="{TRIGGER.DESCRIPTION}" -triggerUrl="{TRIGGER.URL}" -triggerValue="{TRIGGER.VALUE}" -hostName="{HOST.NAME}" -ipAddress="{IPADDRESS}" -eventId="{EVENT.ID}" -date="{DATE}" -time="{TIME}" -itemKey="{ITEM.KEY}" -itemValue="{ITEM.VALUE}" 1>>/var/log/opsgenie/zabbix2opsgenie.log

Nothing happens. OPSGenie doesn't get the alert, and nothing is written to the above logfile. It appears that Zabbix does not call the script.

I did find a line in the /var/log/zabbix/zabbix_server.log stating that the "condition "Trigger value = PROBLEM" was no longer supported. So I have recreated the actions to use Trigger Severity instead but this has not helped.

I don't believe there is a problem on the providers side as the process works fine when run manually.