Page Comparison

...

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 email and API, Jira Service Management can communicate with these tools and process its alerts according to the data they send. With integrations, you can extend your everyday monitoring services with a powerful alert and notification system. Jira Service Management integrates with the services Rackspace, New Relic, Circonus, and more.

Jira Service Management provides gives you a robust framework to so that you can integrate it with all your operations management tools. Through email and APIs, Jira Service Management can communicate with your tools.

View the full list of Jira Service Management integrations.

Integration Types

...

You can forward events from many monitoring tools to Jira Service Management for alerting purposes. 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 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 Jira Service Management's Scout Integration to let Jira Service Management automatically create and close alerts according to events on Scout.

Bidirectional Integrations

...

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

...

is not customizable

Email based Integrations

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

...

The available actions are explained in detail below.

Ignore Action

An ignore 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 Jira Service Management.

From the integration advanced settings 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 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.

Remember that unless you click "Save Integration", To save this action and any customization you made will not be saved, remember to click 'Save Integration'.

Create Alert

A Create Alert action will create a new 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.

To see this in detail, click the plus sign next to "Create ‘Create Alert" under "Actions"' under 'Actions’. This will open up an empty Create Alert action. A Create Alert action has three tabs: Filter and two Alert Fields tabs.

...

If the data that's sent to Jira Service Management matches the condition set of this filter, this Create Alert action will be processed to create an Jira Service Management alert. For more information on Filter, see Action Filters.

Alert Fields

Alert fields constitute are the data an that’s present in a 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 Jira 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, the 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.

...

An Acknowledge Alert action will acknowledge (or ack) an existing 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

...