...
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.
| View file | ||
|---|---|---|
|
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.
...
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.
| View file | ||
|---|---|---|
|
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.
...
Learn more about the dynamic fields.
| Info |
|---|
Share your feedbackWe would love to receive feedback about this documentation, the product experience, functionality, or anything you’ve got to share. (Simpler: Do you have any feedback about this documentation, your product experience, or any functionality? We'd love to hear from you.) You can either add comments to this page or add a card on the Trello board. |
| 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