Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Zabbix alerts are not acknowledged through OpsGenie Edge Connector (oec)

We have installed the OpsGenie WebHook integration with Zabbix, and the OpsGenie Edge Connector.

With this, Zabbix sends alerts to OpsGenie as it should, however alerts acknowledged in OpsGenie are not acknowled in Zabbix. In looking at the Activity Log for the alert in OpsGenie, I can see that the error seems to be originating from the script:

"/home/opsgenie/oec/scripts/", line 138, in <module> main() File "/home/opsgenie/oec/scripts/", line 109, in main "eventids": alert_response.json()['data']['details']['eventId'], KeyError: 'eventId'

I have opened a support case with Atlassian. Has anyone encountered/resolved this issue?

1 answer

1 accepted

1 vote
Answer accepted

Hi John!


This is Justin, the engineer who worked on the original support ticket you opened - I just wanted to add an answer here, in case anyone else runs into a similar issue. 


The root problem here was due to a mixing of Opsgenie's provided integration and Zabbix' native Opsgenie notification method, outlined here:


To use Opsgenie with OEC (which is required for full bi-directional communication), you'll want to be sure to use the notification method described here:


which triggers a script that sends to Opsgenie's Zabbix integration endpoint, and importantly includes the required 'eventId' property, which is used for the OEC integration. When using Zabbix' webhook notification method, the 'eventId' property is not included, thus breaking some of the functionality that allows us to make updates *back* to the source alert in Zabbix.


In the case here, once we added the notification action and command to use the provided script to send to Opsgenie, the full bi-directional flow did begin to work as expected. 


Having said that, if you (or anyone else) runs into a similar issue, please let me know!





Hi Justin,


I have my Zabbix configure the same way as the link that you mentioned in the previous comment. It means using the "Opsgenie Zabbix plugin".


I am able to send the alerts from Zabbix toward Opsgenie but if I try to ack the alert from Opsgenie it doesn't acknowledge the alert in Zabbix. 

Could you please give me some steps to troubleshoot and be able to find the issue?


Thanks in advance,


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events