Running Multiple OEC Services on a Single Host

[#1]

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:

...
[Service]
...
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.).

The port used by OEC for metrics will also need to be changed (or disabled) in the new service (default: 7070)

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>

In Windows, this is updated in the oecService64|32.json file:

"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).