How to Alert Different Teams Through One Integration

[#1]

Advanced integration settings are available only on the standalone Opsgenie Standard and Enterprise plans, and the JSM/O Premium and Enterprise plans.

Account Admins and Owners by default will only have permission to global integrations.

When an integration is global - meaning it is assigned to [No Team] - a Responder field will appear within each create alert action. These actions can be configured under the Advanced tab of the integration:

Opsgenie provides default actions for every integration. You can edit these actions, and add others to meet many use cases - such as alerting different teams through one integration + multiple create alert actions.

For example with a JSM integration - filter on the project key (and/or other fields), and add the corresponding Opsgenie team(s) to be notified for specific alerts:

These actions are reviewed in an order of operations from top → down, and only the first matching action will execute. Once this happens, no further rules are evaluated - so order sometimes matters.

Actions follow a simple WHEN/IF/THEN conditional statement; WHEN a request is sent to Opsgenie, and IF the filter’s condition(s) match, THEN have Opsgenie create an alert, close an existing alert, etc.

With the example above if JSM creates an issue under the COMM project, the top create alert will match and notify the Community Team.

If JSM creates an issue under the DEV project, Opsgenie would skip the top action since its filter and conditions do not match the incoming payload. Opsgenie would then review the following create alert action, which would match and notify the Dev Team:

The same idea can be applied to notify multiple teams about one alert as well: