https://support.atlassian.com/opsgenie/docs/action-filters-in-opsgenie-integrations/
Action filters in
...
Jira Service Management integrations
A filter is a set condition. Many features of Jira Service Management use filters to provide action execution based on certain some conditions. You can customize customise to process integration actions to be processed with certain incoming data, fire callbacks to be fired for particular types of alerts, apply policies to be applied to certain alerts, etcand do a lot more.
For example, Opsgenie Jira Service Management processes every all incoming data associated with your integration; and evaluates from integrations, and then it checks them against your integration's actions for execution. Remember that integration actions have a processing order; and at . At most one action can be executed execute on a single webhook. A filter has a condition set. If the first action's condition set, in other words Filter , does not match the incoming webhook data, Opsgenie Jira Service Management moves on to the next action in line and evaluates its . It then evaluates this action's Filter. If an action's Filter matches the data, Opsgenie Jira Service Management executes that action and . Then it ends the processing on that particular webhook. If it finds no matching action is found, nothing happens.
The figure below shows a Create Alert action's Filter. Its condition match type is set to 'Match one or more conditions below'; so . In the incoming data if the variable 'Status Message ' in the incoming data is equal to 'Failed' or 'Still Failing', then Jira Service Management creates an Opsgenie alert will be created according to the setup specified in the Alert Fields; and the . The processing will end there. If, however,
But if an incoming data with 'Status Message' equal to something other than these comes to OpsgenieJira Service Management, it will be evaluated check it against the Create Alert action and when . When that doesn't match, the Filter of the Close Alert below will be processedprocess.
| View file | ||
|---|---|---|
|
Opsgenie Jira Service Management provides default actions with pre-configured Filter and Alert Fields for every integration. However; , you can customize them any way you like: you can edit them, delete them or add new actions of your own.
...
Match all alerts: When this option is selected, the integration action will match every data that's evaluated against it and cause the action to be executed. No specific condition is specified when this option is selected.
Match one or more conditions below: With this option selected, if any one of the conditions that are specified in the condition set matches the incoming data, it's sufficient for Opsgenie Jira Service Management to go on and execute the integration action.
Match all conditions below: With this option selected, it's required for the webhook data to match every specified condition in the condition set. If any of them fails, the action will not be executed and Opsgenie Jira Service Management will move on to the next integration action to process, if there is any.
...
Learn how to use Opsgenie's Jira Service Management’s integration framework
Show more
Action filters in Opsgenie Jira Service Management integrations
Dynamic fields in Opsgenie Jira Service Management integrations
String processing methods in Opsgenie Jira Service Management integrations
Show more
On this pageCondition OperationsAlert Fields section
...