Page Comparison

https://support.atlassian.com/opsgenie/docs/use-advanced-integration-settings/

...

Overview

With the advanced integration settings, you get the most customizations for alerting. You can define when the system should create an alert, execute a close action, automatically acknowledge an alert, or add a note. The framework also enables you to You can also parse out anything from your webhook data and use it dynamically to build your alert content.

The rules execute in top-down order. The first matching rule will execute executes first and it stops evaluating further rules. Learn more about integration types and actions.

You’ll find the rules You can find the actions (Ignore, Create Alert, Close Alert, Add Note) in Advanced settings, under the Actions titlethe Add rule dialog.. The rules are responsible for processing the action processingactions. 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 filters section. The first rule , matching your alert (with a top-down order) , will execute executes the action associated with it. The Alert Fieldsproperties section provides the details of that action. Your alert will be is created according to the template capture captured in the Alert Fields propertiessection.

Action Processing

...

Action processing

The advanced settings consist of many different alert scenarios. These scenarios are called “Actions” “actions” and specify how and when alerts can be created, closed, or acknowledged. Jira Service Management provides default actions for every integration. But you You can customize them and add as many actions as you like. For example, you can have three Create Alert actions. This means the webhook data that comes to Jira Service Management will be evaluated against these three scenarios in order. If one of them has a match, a new alert will be created.

...

Learn more about actions.

Action filters

Every action has a filter section. Jira Service Management processes every incoming data associated with your integration. Then it evaluates them against your integration's actions for execution. Integration actions have a processing order, and a request executes only one action. If the first action's condition set, Filter does not match the incoming payload, Jira Service Management moves on to the next action in line and evaluates its Filter. If an action's Filter matches the data, Jira Service Management executes that action and ends the processing on that particular webhook. If it finds no matching action, nothing happens. Pre-canned integration has a list of prepared filter options. The most common ones are available, tailored to the integration you choose. Learn more about action filters in integrations.

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

...

Alert properties

The action executes 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. If the variable Action in the incoming data is equal to Create and the Source Type Name variable equals Monitor Alert, then a Jira Service Management alert will be created according to the setup specified in the Alert Fields. And the processing will end there.

...

On the right side, you'll find draggable fields (blue boxes). You'll also see dynamic fields captured in some of the default alert fields (those inside the curly brackets). Using these, Jira Service Management parses your data to construct rich and informative alerts. You can use dynamic fields to customize alert properties . This will automatically parse 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.

Info

Share your feedback

We would love to receive feedback about this documentation, the product experience, functionality, or anything you’ve got to share.