Allow OEC (Opsgenie Edge Connector) Integration to define filters per Action

User Problem

Within the standalone OEC integration, It's possible to define a Filter in the "Post Actions to OEC for Opsgenie Alerts". However this filter applies to all actions - including "a custom action is executed on an alert". This prevents us from having a filter for "alert is created", and still allowing other OEC Custom Actions to go through for alerts that do not match the filter. The filter is applied to all actions.

Suggested Solutions

This section should allow you to create multiple actions much like the advanced settings in integrations. Each choice should allow you to define a specific filter, or it should be possible to define multiple filters and create actions for the different filters

Filter A (All issues with tag externalUpdate):
if alert is created in Opsgenie, post action to OEC
if a tag is added to the alert in Opsgenie, post action to OEC, in OEC for these tags: externalUpdate

Filter B: (Match all Alert)
if a custom action is executed on alert in Opsgenie, post action to OEC, for this custom action: ACK-SITEWIDE
if a custom action is executed on alert in Opsgenie, post action to OEC, for this custom action: Reticulate-Splines

Current Workarounds

Multiple OEC Instances can be run, each catering to a different Filter, with a different OEC integration that has a different filter defined.

Alternatively, the logic can be be included in the OEC Scripts, so that all create alert actions go through to OEC, and the script that is mapped to the "create" action has conditional logic in it that defines if it runs for the particular payload provided to the OEC instance.