Page Comparison

https://support.atlassian.com/opsgenie/docs/what-are-the-integration-types-and-actions/

...

OpsgenieJira Service Management's Integrations Framework allows Opsgenie's Jira Service Management’s alerting capability to work in conjunction with most popular monitoring tools. Through e-mail and API, Opsgenie Jira Service Management can communicate with these tools and process its alerts according to the data they send. With Opsgenie Jira Service Management integrations, you can extend your everyday monitoring services with a powerful alert and notification system. Among the services Opsgenie Jira Service Management integrates with are Rackspace, New Relic, Circonus, and more.

Opsgenie Jira Service Management provides a robust framework to integrate Opsgenie Jira Service Management with all your operations management tools. Through email and APIs, Opsgenie Jira Service Management can communicate with your tools.

View full list of Opsgenie integrations.

Integration Types

Opsgenie Jira Service Management Integrations Framework can operate different types of integrations.

...

Bidirectional Integrations

OpsgenieJira Service Management's bidirectional integrations allow data to be sent and processed both ways between Opsgenie and the other application. A good example is our ServiceNow integration. Using the integration, ServiceNow sends incident events to Opsgenie, with detailed information and Opsgenie forwards alerts as incidents to ServiceNow.

Outgoing Integrations

Opsgenie Jira Service Management Integrations Framework has callback capability that can notify chat applications about Opsgenie events. A good outgoing integration example is our Webhook capabilities which pushes information via an URL endpoint. It's important to note that this information cannot be customized.

E-mail based Integrations

You can use Opsgenie Jira Service Management e-mail integrations to process your incoming e-mails for alert management. Opsgenie Email Integration accepts any kind of e-mail and is fully customizable; allowing you to control a robust alerting mechanism tailored to your inbox. Opsgenie Jira Service Management has also specific e-mail based integrations for several monitoring tools, e.g Pingdom, Uptime Robot, Zenoss etc. For example, if you're a Pingdom customer, you can add Opsgenie's Pingdom Integration and readily turn Pingdom events into Opsgenie alerts.

...

Alert fields constitute the data an Opsgenie alert is composed of. The fields that you can configure are explained below. You can write text, and also drag and use the dynamic fields from the right. For more information on draggable fields, see Dynamic Fields.

• Message: Alert text up to 130 characters.

• Alias: The alias is the unique identifier for "open" alerts. There can only be one "open" alert with the same alias in Opsgenie.

• Recipients: The names of the users, groups, escalations and schedules that should be used to determine who should be notified. Note that for a Create Alert action, Message and Recipients fields are mandatory.

• Entity: The name of the entity that the alert is related to. For example, name of the application, server etc.

• Source: The source of the alert.

• Tags: Labels to the alert for easier identification and categorization of alerts. Use commas in between for multiple tags.

• Actions: List of actions a recipient can execute to respond to an alert. Use commas in between for multiple actions.

• Description: Detailed description of the alert; anything that may not have fit in the Message field can be entered here.

• Extra Properties: Additional alert properties. Enter the name of the property in the first field and the value in the second.

• User: Owner of the note that will be added to the alert.

• Note: Note to be added to the alert.

...

• User: Owner of the note that will be added to the alert.

• Note: Note to be added to the alert.