• Products
  • Get started
  • Documentation
  • Resources

Use advanced integration settings

Advanced integration settings are only available on Opsgenie’s Standard and Enterprise plans.

If you’re using Opsgenie as part of your Jira Service Management, advanced integration settings are available on Jira Service Management’s Premium and Enterprise plans.

Opsgenie integrations may have two types of settings: Basic and Advanced. Basic settings are located on the main screen of an integration.
Using the advanced integration settings will empower you to customize your alerting fully. You can define when the system should create an alert and execute a close action, acknowledge an alert automatically, or add a note.
The framework also enables you to parse out anything from your webhook data and use it dynamically to build your alert content.
The rules are executed in top-down order, and the first matching rule will execute - no further rules are evaluated. Learn more about integration types and actions.

A screenshot showing the location of the Advanced button in an integration.

When you go to the Advanced settings, you’ll find the rules (Ignore, Create Alert, Close Alert, Add Note) under the Actions title. The rules are responsible for the action processing. Every time data lands on the endpoint (or email box), these rules are matched to the data in top-down order. Each of these rules has a Filter section. The first rule, matching your alert (with a top-down order), will execute the action associated with it. The Alert Fields section provides the details of that action - your alert will be created according to the template capture in the Alert Fields section.

Integrations work best with real alerts. We recommend not to use test buttons in third-party tools when setting up a new integration.

Action Processing

Integration advanced settings consist of many different alert scenarios. These scenarios are called “Actions” and specify how and when alerts can be created, closed, acknowledged… Opsgenie provides default actions for every integration, but you can customize them and add as many actions of your own as you like. You can, for example, have three Create Alert actions, which means the webhook data that comes to Opsgenie will be evaluated against these three scenarios in order; and if one of them has a match, a new alert will be created.


A screenshot showing the advanced actions in an Opsgenie integration.

Action Filters

Every action has a filter section. Opsgenie processes every incoming data associated with your integration; and evaluates them against your integration's actions for execution. Remember that integration actions have a processing order, and at most, one action can be executed by a single request. If the first action's condition set, Filter does not match the incoming payload, Opsgenie moves on to the next action in line and evaluates its Filter. If an action's Filter matches the data, Opsgenie executes that action and ends the processing on that particular webhook. If no matching action is found, nothing happens.
Pre-canned integration has a list of prepared filter options - the most common ones are available, tailored to the integration you chose. Learn more about action filters in integrations.

Also, find out which regular expressions you may use to customize and filter alerts.

Alert Fields

The action will be executed according to the template and settings you capture here. The figure below shows a Create Alert action's Filter. Its condition match type is set to Match all conditions. So if the variable Action in the incoming data is equal to Create and the Source Type Name variable equals Monitor Alert, then an Opsgenie alert will be created according to the setup specified in the Alert Fields; and the processing will end there.

An image showing a draggable field in an integration setting.

On the right side, you see draggable fields (blue boxes), and you see these dynamic fields captured in some of the default alert fields (those inside the curly brackets). Using these, Opsgenie parses your data to construct rich and informative alerts. You can use dynamic fields to customize alert properties - basically automatically parsing out a variable from the payload every time you create an alert according to this "Alert Fields" section.
If you don't need the whole variable and need only a part of the data, like a certain part of an email subject, you can use one of the string processing methods.

Learn more about the dynamic fields.


Additional Help