You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Our IT security team is mandating all outbound connections through our proxy servers should be authenticated (BasicAuth or NTLM). I'm not seeing anything in the OEC setup docs about adding this authentication. Has anybody gotten this working?
Justin here, from Opsgenie support - happy to help!
You should be able to your proxy configuration (with authentication) in the environment variables defined in the OEC service file. So, for basic auth, it might look something like this (examples below for both Windows and Linux OEC service files):
You can add the HTTP_PROXY and HTTPS_PROXY values with authentication in the 'Env' field in the oecService.json file.
"Name": "OEC Service",
"DisplayName": "OEC Service",
"Description": "Run the OEC Service",
"OECPath" : "C:\\opsgenie\\opsgenie-oec\\OpsgenieEdgeConnector32.exe",
"Args" : ["-oec-metrics", "7070"],
Note - if OEC is already installed then you will need to reinstall OEC. The uninstall command (adjust accordingly for 32 or 64 bit OEC) is:
the install command is:
You'll add your HTTP/HTTPS_PROXY info as Environment variables called out in the oec.service file:
Once these have been added, you'll need to reload and restart the service:
systemctl restart oec.service
That should get you started, but please let us know if you have any issues getting the proxy working. Thanks!
Atlassian Cloud Support