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

Resolve Incidents Faster with Additional Action Channels for OEC

Today we are excited to announce that Opsgenie Edge Connector (OEC) channel for Opsgenie Actions is now available. 

As a refresher, OEC is an application that makes it possible for Opsgenie to integrate with systems that are behind a firewall and are not accessible from the public internet. 

Regardless of whether you integrate cloud monitoring, ITSM tools, or on-prem systems with Opsgenie, OEC enables you to pass data from Opsgenie back to your environment keeping the data in-sync across your organization and secured. Using these channels enables teams to resolve alerts faster with the click of a button. Once OEC is set up, additional buttons are added to the alert so that the actions you defined can be taken quickly. 

action channel screenshot.png


Let’s look at an example to illustrate how this new channel works. 

An alert comes into Opsgenie from an on-premise server notifying the on-call responder that CPU levels are abnormally high. From the alert dashboard in Opsgenie, the on-call engineer can take the action “add new instance” directly from the alert drop-down menu.  At this point the OEC integration will route this action back to the server, executing the script as it was defined during the setup. Most importantly, this new action channel allows the responder to define specific parameters such as the size of the instance and/or the number of instances to add in addition to simply executing the script. This gives your on-call team more granular control over how the action is executed.   

Setting up an Opsgenie Edge Connector Channel:

Go to the Actions tab from your Team dashboard. 

Click Add Action Channel, enter the name of the channel and select Opsgenie Edge Connector (OEC) as the type then click Create.

Create Action Channel.pngCopy the API key provided. Keep it handy, as you will need to paste it into your Edge Connector configuration once you have installed it.

Create Action Channel 2.png

Things to Note:

  • OEC action channel is compatible with versions of OEC which are 1.0.2. or above.
  • Do not set up a separate OEC integration from your Integrations page. Simply install OEC in your environment and use the API key provided to you during the setup of the action channel.


Helpful links to get started:




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events