...
Jira Service Management's Integrations Framework allows Jira Service Management’s alerting capability to work in conjunction with the most popular monitoring tools. Through e-mail and API, Jira Service Management can communicate with these tools and process its alerts according to the data they send. With Jira Service Management integrations, you can extend your everyday monitoring services with a powerful alert and notification system. Among the services Jira Service Management integrates with are the services Rackspace, New Relic, Circonus, and more.
Jira Service Management provides a robust framework to integrate Jira Service Management with all your operations management tools. Through email and APIs, Jira Service Management can communicate with your tools.
View the full list of Opsgenie Jira Service Management integrations.
| Info |
|---|
If the Owner owner of your Jira Service Management account has not verified their email yet, users within your organization will not be able use API integrations. |
...
You can forward events from many monitoring tools to Opsgenie Jira Service Management for alerting purposes. Opsgenie Jira Service Management is able to catch and process notification webhooks and create well-informed alerts based on the notification data. With this ability you can let Opsgenie Jira Service Management process any HTTP request as well as using many API-based integrations configured specifically for monitoring tools. For example, if you're a Scout customer, you can use OpsgenieJira Service Management's Scout Integration to let Opsgenie Jira Service Management automatically create &and close alerts according to events on Scout.
| Info |
|---|
If the Owner owner of your Opsgenie Jira Service Management account has not verified their email yet, users within your organization will not be able use API integrations. The owner of your Jira Service Management account has to verify emails of users within your organization so that they can use API integrations successfully. |
Bidirectional Integrations
Jira Service Management's bidirectional integrations allow data to be sent and processed both ways between Opsgenie Jira Service Management and the other applicationapplications. A good example is our ServiceNow integration. Using the integration, ServiceNow sends incident events to OpsgenieJira Service Management, with detailed information and Opsgenie Jira Service Management forwards alerts as incidents to ServiceNow.
...
Jira Service Management Integrations Framework has callback capability that can notify chat applications about Opsgenie Jira Service Management events. A good outgoing integration example is our Webhook capabilities which pushes information via an a URL endpoint. It's important to note that this information cannot be customized.
...
You can use Jira Service Management e-mail integrations to process your incoming e-mails for alert management. Opsgenie Jira Service Management Email Integration accepts any kind of e-mail and is fully customizable; allowing you to control a robust alerting mechanism tailored to your inbox. 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 OpsgenieJira Service Management's Pingdom Integration and readily turn Pingdom events into Opsgenie Jira Service Management alerts.
Integration Advanced Settings
Integration advanced settings consist of many different alert scenarios. These scenarios are called "Actions"; and they specify how and when alerts can be created, closed, acknowledged. etc. There are default actions provided by Opsgenie Jira Service Management 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 ‘Create Alert’ actions; which means the webhook data that comes to Opsgenie Jira Service Management will be evaluated against these three scenarios in order; and if one of them has a match a new alert will be created.
...
There is a specific order to which type of actions will be evaluated first. For example, by design Ignore ‘Ignore’ actions are evaluated first and Add Note ‘Add Note’ actions are evaluated last. This means the incoming data will be evaluated against Ignore ‘Ignore’ actions; and if one of them has a match then Add Note ‘Add Note’ actions and also any other action will not be evaluated at all; and only that Ignore action will be processed.
...
An ignore action means that the webhook data, if it matches the action's filter, will be ignored completely; and will not be evaluated by any other action. Ignore actions are the first actions to be processed when a webhook data comes to OpsgenieJira Service Management.
From the integration advanced settings page, under Actions on the right, click the plus sign next to "Ignore". This will open a new ignore action. You'll see that an ignore action has one tab, Filter. If a webhook data matches the condition set of this filter, the ignore action will be processed, thus, the data will be ignored. For more information on Filter, see Action Filters.
...
A Create Alert action will create a new Opsgenie Jira Service Management alert if the condition set of its filter matches the data. You can not only specify the conditions to when an alert will be created, but you can also fully customize what kinds of information it will have and where, its formatting etc.
...
If the data that's sent to Opsgenie Jira Service Management matches the condition set of this filter, this Create Alert action will be processed to create an Opsgenie Jira Service Management alert. For more information on Filter, see Action Filters.
...
Alert fields constitute the data an Opsgenie Jira Service Management 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 OpsgenieJira Service Management.
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.
...
A Close Alert action will close an existing Opsgenie Jira Service Management alert based on its alias; if the data matches the condition set of the action's Filter. For more information on Filter, see Action Filters
...
Alias is mandatory in the alert fields of a Close Alert action. When a Close Alert action is processed, Opsgenie Jira Service Management looks for an "open" alert to close, whose alias is equal to the Alias specified in the Close Alert action.
...
Alias is mandatory in the alert fields of an Acknowledge Alert action. When an Acknowledge Alert action is processed, Opsgenie Jira Service Management looks for an "open" alert to ack, with alias equal to the Alias specified in the Acknowledge Alert action.
...
Add Note action is used to add a comment to an existing alert according to the data Opsgenie Jira Service Management API receives. When an Add Note action is processed, Opsgenie Jira Service Management looks for an alert to add note to, with alias equal to the Alias specified in the Add Note action.
...