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!


Running Multiple OEC Services on a Single Host

This article will show you how to install multiple, unique Opsgenie Edge Connector (OEC) services on a single host.


The main use case for this is using OEC across multiple integrations in Opsgenie. A couple of examples of this are: 


  • Using a separate Jira integration for each project/team in Opsgenie. While these alerts are going back to the same Jira server, OEC can only accept a single integration’s API key at a time. 

  • Using Nagios for infrastructure monitoring and Jira for issue tracking. Each integration will need its own OEC service to push actions back. 


First, make a copy of the current service and config files:


# cp /home/opsgenie/oec/config.json /home/opsgenie/oec/two/config.json
# cp /etc/systemd/system/oec.service /etc/systemd/system/oec-two.service


Next, point oec-two.service to the new config file:


Environment="OEC_CONF_SOURCE_TYPE=local" "OEC_CONF_LOCAL_FILEPATH=/home/opsgenie/oec/two/config.json"


Make sure you update the needed fields in the new config file (API key, script path, etc.).



In Linux, this is updated in the ExecStart line of /etc/systemd/system/oec-two.service:


ExecStart=/usr/local/bin/OpsgenieEdgeConnector -oec-metrics <port-number>


"Args" : ["-oec-metrics", "7070"],


Finally, enable and start oec-two.service:


# systemctl enable oec-two.service
# systemctl start oec-two.service


At this point, both oec.service and oec-two.service should be active and running. Confirm they are polling the correct queues by triggering actions for each integration in Opsgenie.


In order to ensure that we continue to provide useful content, please let us know if this Article is helpful (Thumbs Up/Down). Also, to help us improve, feel free to provide additional feedback (directly in the community).



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events