Filter alerts by integration?

[Emma Rector]

Is there a native way to look at the integration directly for conditions? I want to provide multiple APIs so that users creating an alert manually specify what they are working with (e.g. Oracle vs. Sql Server databases). Depending on which API is used, I would like to apply different routing rules to it, because different people know how to handle the two types of things.

Filtering on the integration name directly would be the easiest. It shows up well when I create an alert:

(source is my email address because I manually created an alert for testing) . The Integration field also works well for other integrations, showing the name defined on the Integrations page.

But that doesn't seem to be a selectable field when creating conditions (on routing rules, policies, etc.):

(not shown: Actions, Alias)

I have tried the following as routing rule conditions, and the activity logs show that they did not work:

• Details (Key-Value Based) Integration Contains DBA_API
• Details (Key-Value Based) API Equals DBA_API
• Details (Key-Value Based) API Equals DBA_API (API)
• Details Contains DBA_API
• Entity Equals DBA_API

I know I could use the Create Alert rule on each API to add a tag/add an extended property/change properties like the message, alias, or description to mark which API is being used, but it seems like there should be something built in to handle this.

[John M · Accepted solution]

Hi @Emma Rector ,

John from Opsgenie support here, happy to assist. 

The value in the 'source' field is typically a hard-coded value that is the same as the type of integration. For example, for a Twilio integration it looks like this, by default:

Only with API integrations is the default value {{source}}, which parses to the users email address. 

As seen above, the entity field is also usually blank by default, so that you can configure it for things like routing rules.