AWS SNS integration.

Dmitry Petriev

Hi, 

 

We are using the following flow: AWS Managed Prometheus connected to AWS SNS (through Alertmanager configuration), and AWS SNS sent an alert to OpsGenie.

 

We have rules in AWS Managed Prometheus that send alerts to OpsGenie; integration works well, but we want additional settings:

1) How can we set tags in OpsGenie alerts that depend on triggered rules?

2) How can we close the FIRING alert after getting RESOLVED alert? Now, OpsGenie creates two issues related to the same alert.

 

I have doubts about this flow because I know that AWS SNS and AWS Managed Prometheus don't have such a flexible setup.

John M_2hpypf

Hi @Dmitry Petriev

Below are answers to your questions:

1) How can we set tags in OpsGenie alerts that depend on triggered rules?

You will need to add multiple 'create alert' actions in the integration's advanced settings. Each 'create' action will have its own unique filters that trigger different tags to be added. Here is a screenshot:

2) How can we close the FIRING alert after getting RESOLVED alert? Now, OpsGenie creates two issues related to the same alert.

The alias on the close alert will need to match the alias on the payload that created the alert. The alias field is what the system uses to match incoming payloads with open alerts, to either de-duplicate them (if they match a 'create alert' action), close them (if they match a 'close alert' action) or complete other actions like 'add note' or 'acknowledge' if the filters match those actions. Keep in mind that incoming payloads are processed against the actions from top to bottom, so if an incoming payload matches a 'create alert' action and there is an open alert with the same alias, it will deduplicate, even if it also matches a 'close' action, because the 'create' actions are processed before close actions - so be sure that your filters are specific and do not broadly match against payloads that they should not be.