https://support.atlassian.com/opsgenie/docs/use-advanced-integration-settings/
Advanced integration settings are only available on Opsgenie’s Standard and Enterprise plans.
...
| Info |
|---|
Advanced integration settings are available on Jira Service Management’s Premium and Enterprise plans. |
Opsgenie Jira Service Management integrations may have two types of settings: Basic and Advanced. Basic settings are located You'll find basic settings on the main screen of an integration.
Using With the advanced integration settings will empower you to customize your alerting fully, you get the most customizations for alerting . You can define when the system should create an alert and , execute a close action, automatically 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 execute in top-down order, and the . The first matching rule will execute - no first and it stops evaluating further rules are evaluated. Learn more about integration types and actions.
| View file | ||
|---|---|---|
|
When you go to the Advanced settings, you’ll You’ll find the rules (Ignore, Create Alert, Close Alert, Add Note) in Advanced settings, under the the Actions title 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 a Filter section section. The first rule, matching your alert (with a top-down order), will execute the action associated with it. The The Alert Fields section section provides the details of that action - your . Your alert will be created according to the template capture in the the Alert Fields Fields section.
Integrations work best with real alerts. We recommend not to When setting up a new integration, we recommend to not 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 acknowledged. Jira Service Management provides default actions for every integration, but . But you can customize them and add as many actions of your own as you like. You can, for For example, you can have three Create Alert actions, which . This means the webhook data that comes to Opsgenie Jira Service Management will be evaluated against these three scenarios in order; and if . If one of them has a match, a new alert will be created.
...
Every action has a filter section. Opsgenie Jira Service Management processes every incoming data associated with your integration; and . Then it evaluates them against your integration's actions for execution. Remember that integration Integration actions have a processing order, and at most, a request executes only one action can be executed by a single request. If the first action's condition set, Filter does not match the incoming payload, Opsgenie Jira Service Management moves on to the next action in line and evaluates its Filter. If an action's Filter matches the data, Opsgenie Jira Service Management executes that action and ends the processing on that particular webhook. If it finds no matching action is found, nothing happens.
Pre-canned integration has a list of prepared filter options - the . The most common ones are available, tailored to the integration you chosechoose. 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 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 to Match all conditions. So if If the variable Action in the incoming data is equal to Create and the Source Type Name variable equals Monitor Alert, then an Opsgenie a Jira Service Management alert will be created according to the setup specified in the Alert Fields; and . And the processing will end there.
...
On the right side, you see 'll find draggable fields (blue boxes), and you see these . You'll also see dynamic fields captured in some of the default alert fields (those inside the curly brackets). Using these, Opsgenie Jira Service Management parses your data to construct rich and informative alerts. You can use dynamic fields to customize alert properties - basically automatically parsing . 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.
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Criteria for checks |
- Replacing OG with JSM
- Basic grammar & spell check
- US English
- Positive language
- Removing passive voice (wherever necessary)
- Simplifying sentences
- Change V&T
- Replacing old links with new ones