OpsGenie can send an HTTP POST request to a web-accessible URL endpoint (what's often referred as webhooks) and pass alert activity data. URL endpoint can be any platform, web server, etc. as long as the URL is accessible from the Web. Webhook data includes the alert activity (create, acknowledge, etc.) as well as a subset of the alert fields (alertId, username, alias, entity, userId) as part of the HTTP request payload (JSON). Also, users can define custom headers to add the webhook call. Moreover, you can enable sending the alert description and alert details by simply checking the related boxes.
Integration can be created at OpsGenie Webhook Integration page.
OpsGenie allows customers to define action mappings between OpsGenie actions and JIRA actions.
You can use this section to post OpsGenie actions to the given url. For example, you can add post to the url, when the alert is created. In order to do this, you should define If alert is created in OpsGenie, post it to url. mapping.
- a tag is added to the alert and a custom action is executed on alert actions differ from other actions. When you select one of these actions, you'll see an extra field to enter for which tags or for which custom action this mapping will work.
- You can enter multiple tags by separating the tags with a comma. If you enter multiple tags, the mapping will work if the alert has one or more of the specified tags. You can also leave the tags field empty, if you would like the mapping to work for any tag.
- If you map an OpsGenie action to multiple JIRA actions, you will get an error except for the a tag is added to the alert and a custom action is executed on alert actions. You can save multiple mappings for these actions, because they will differ by the given tags and the given custom action names.
Example Webhook data for different actions can be found in this document.