Opsgenie Alert routing teams within teams

[Matthew Day]

We have a technology department that consists of 3 teams as well as a NOC. We have alerts coming into Opsgenie from several monitoring sources. 

How can I route alerts to the correct team without manual triage? I've not found good documentation for the conditions available under routing rules.  (Actions, Alias, Description, Entity, Details, Details (Key-Value Based), Message, and Priority)

i.e. Icinga2 monitoring reporting a server problem should route to the server team while Icinga2 monitoring reporting a switch problem should route to the network team. 

Further, having ONE change control for all of technology is also a goal. Is change management project-specific (like requests) or is it tenant-specific (like opsgenie)? 

[Nick Haller]

Hi @Matthew Day ,

Under the integrations Advanced tab, you can filter on the data being sent from Icinga2 >> Opsgenie, and map certain alerts to certain teams.

Note this tab is only available on certain plans such as the standalone Opsgenie Standard and Enterprise plans, as well the JSM Premium and Enterprise plans:

^ This create alert action filters on the Service Group Name, and if it contains Network, send to the Opsgenie Network team.

Multiple create alert actions can be configured. If the top action does not match the defined filter/conditions, Opsgenie will look at the following action(s) until a match it met.