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

Can Zabbix OEC support multiple integrations?

Have Zabbix v5.0 w/ OEC v1.1.4 ... the config.json only allows for a single api_Key, yet we need Zabbix to notify multiple different application teams.   I know that we can specify a responder in the call to send2opsgenie, but the issue is all other teams are stuck with the integration settings the primary integration uses, which in my case suppresses alerts.   Thus, all other teams have their alerts suppressed.

I attempted to setup a 2nd OEC agent, with a separate config.json.   When I start it, I get an error stating it is unable to bind to a tcp port (as the primary oec process has it bound).   I'm finding no documentation or way to specify a secondary port for it to listen on.   Nor am I sure it would even work bound to a different port.

1 answer

1 accepted

1 vote
Answer accepted
Connor Eyles Atlassian Team Jul 04, 2021

Hi @DMC 

Yes, you can run multiple OEC services on a single host smile

When it comes to setting up your secondary OEC to run on another port here are some steps on how you can do this: 


Editing the Linux service


  1. Edit /etc/systemd/system/oec_custom.service change the line ExecStart=/usr/local/bin/OpsgenieEdgeConnector add the parameter --oec-metrics with a unique port value (the default value is 7070) for exampleExecStart=/usr/local/bin/OpsgenieEdgeConnector --oec-metrics 7071

  2. Edit /etc/systemd/system/oec_custom.service change the line Environment="OEC_CONF_LOCAL_FILEPATH=/home/opsgenie/oec/conf/config.json" edit it to reflect the new path of config.json Environment="OEC_CONF_LOCAL_FILEPATH=/home/opsgenie/oec/conf/config.json" (See the paths highlighted green in the screenshots below)

  3. Lastly, enable the service to start after system boot: systemctl enable oec_custom

Image 2021-07-05 at 2.41.47 pm


Image 2021-07-05 at 2.42.57 pm


Creating a new Windows Service

Edit oecService64.json update the service name (highlighted pink), oec-metrics port (highlighted green) and update the file paths to reflect the new folder’s path (highlighted blue).

Image 2021-07-05 at 2.47.29 pm
Image 2021-07-05 at 2.47.44 pm
Install and start the new service:
cd "c:\opsgenie\oec_custom"
.\oecService64.exe install
.\oecService64.exe start

Thanks Connor.   Appreciate the timely response.

Here's what I've learned, while testing this.   I'm not sure you need multiple OEC agents running.   I found that the OEC agent is only used during INBOUND communications.   I was under the impression that the send2opsgenie command was using it for outbound.

Seems the OpsGenie integration can be selected by specifying the '-apiKey=xxxxx' flag to my 'send2opsgenie' command.

The other observation, was than while running two OEC agents, there was no difference.  Both agents seem to be pulling from the same OpsGenie cloud queue.   Such that when an event/alert is acknowledged both of them would attempt to action it.

At this point, I don't believe I see a need to have more than a single OEC agent.   However, I certainly appreciate the response Connor.

Like Connor Eyles likes this
Connor Eyles Atlassian Team Jul 06, 2021

Hi @dmc 

You are correct, OEC is used for inbound communication. Glad to hear you got this one working regardless!

The above steps are how you can run multiple OEC agents on different ports smile


Like Steffen Opel _Utoolity_ likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events