Connection between OEC and Opsgenie

[Denis Dugar]

Hi,

Our team uses Opsgenie and OEC with local scripts for processing alerts. For the best experience and better understanding of processes, we want to know how the connection between OEC and Opsgenie exact works. How long has this connection been working without interrupts and how many alerts it can send between Opsgenie and OEC and how long it is waiting for sending new alerts while we process with one alert? From this question (https://community.atlassian.com/t5/Opsgenie-questions/Firewall-rules-for-OEC/qaq-p/1362588), we understand that Opsgenie creates sqs queue and OEC uses this queue. So also question is what settings this sqs queue has?

[John M]

Hi @Denis Dugar ,

This video and article give a good explanation of how OEC works:

https://www.atlassian.com/blog/opsgenie/edge-connector-for-opsgenie

To answer your other questions:

How long has this connection been working without interruptions?

• OEC is setup independently on each client's servers so as long as the client can reach out to an SQS queue, there should be no interruptions. 

How many alerts be sent between Opsgenie and OEC?

• There is no limit on the number of alerts that can be sent. A single Amazon SQS message queue can contain an unlimited number of messages. However, there is a 120,000 quota for the number of inflight messages for a standard queue and 20,000 for a FIFO queue. Messages are inflight after they have been received from the queue by a consuming component, but have not yet been deleted from the queue.”

What is the waiting period for sending new alerts while alerts are processed?

• Alerts are sent to the SQS queue as they are received. There is no waiting or processing period

What are the SQS settings?

We don't have all of the SQS settings available publicly but here are the settings we have posted:

• US endpoint 1: sqs.us-west-1.amazonaws.com
• US endpoint 2: sqs.us-west-2.amazonaws.com
• Message retention: can be set between 1-14 days. 14 days is our default