Opsgenie to Opsgenie Integration

Alert replication is desired among various scenarios. However, alert synchronization may be required to be different, and this is where the integration configuration differs. Synchronization is ensured via mapped alert actions, thus configure action mapping as warranted by the likely different scenarios.

Below, there are configuration examples for three different use cases. In the remaining part of the document, the MSP’s Opsgenie account is defined as the “main account” and MSP’s customer’s account as the “sub-account”.

Fully synchronize alerts between accounts

With this configuration, if an alert in the main account is acknowledged, then the same alert in the sub-account is acknowledged as well, and vice versa. Similarly, when an alert in the main account is unacknowledged/closed or a note is added to this alert, the same action is applied to the corresponding alert in the sub-account.

Configuring the main account looks like the following:

Configuring the sub-account looks like the following:

Mapped actions can be chosen among create, acknowledge, unacknowledge, close and add note actions. Therefore, integration provides full synchronization for those actions only.

Execute alert actions only in sub-accounts

The desired behavior for this scenario is to execute actions on alerts only in sub-accounts and just inform the main account about the executed alert action. For instance, when the alert in the sub-account is acknowledged, a note like “John acknowledged alert: “test alert” “ is added to the main account’s corresponding alert. Similarly, if the alert in the sub-account is closed, “John closed the alert: “test alert” " note is added to the main account’s alert. In order to do so, configure the integration as follows:

Configuring the main account:

Configuring the sub-account:

Execute alert actions only in main account

This is the opposite of the second scenario. In this scenario, alert actions are executed in the main account, and notes reporting these actions are added to the corresponding alerts in the sub-account in return. For example, when an alert in the main account is unacknowledged, a note such as “John unacknowledged the alert: “test alert” ” is added to the corresponding alert of the sub-account. Below is the configuration supporting this scenario.

Configuring the main account:

Configuring the sub-account: