Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Integrate with Outlyer
If you’re a customer who shifted your operations from Opsgenie to Jira Service Management, adding new instances of this integration isn’t possible in Jira Service Management. You can only edit the integrations that originally shifted from Opsgenie.
What does Jira Service Management offer Outlyer users?
The Outlyer platform allows customers to configure highly customizable Alerts and take actions based on the chosen criteria in order to highlight or be notified of events of interest. With the Outlyer integration, Jira Service Management acts as a dispatcher for these alerts, determines the right people to notify based on on-call schedules– notifies them using email, text messages (SMS), phone calls, and iPhone & Android push notifications, and escalates alerts until the alert is acknowledged or closed.
Functionality of the integration
An alert is triggered when a defined "criteria met" , an alert is also created in Jira Service Management automatically through the integration.
When the alert "criteria is not met" in Outlyer, the alert is also closed in Jira Service Management.
Edit Outlyer integration in Jira Service Management
To edit a Outlyer integration in Jira Service Management, complete the following steps:
Go to your team’s operations page.
On the left navigation panel, select Integrations.
Search for your Outlyer integration.
Edit the integration settings and rules as necessary.
Configure the integration in Outlyer
Use the instructions in this section if applicable.
In Outlyer, open the "Alerts" screen from the side menu.
Create a new alert or edit an existing alert.
Select "Actions" tab of the upper menu.
Click Add New Action and select "Call a Webhook".
5. Paste the API URL into the Webhook URL field.
6. Click Test Webhook.
7. Click Create New Action.
Sample payload sent from Outlyer
Create Alert payload:
JSON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
{
"event": "ALERT",
"rule": "Wordpress",
"account": "default",
"event_type": "trigger",
"entity_id": "572eb7099b36dd8ef71f3f61",
"triggers": [
{
"sources": [
{
"name": "ip-172-31-18-138",
"tags": [
"all",
"wordpress"
],
"timestamp": "2016-06-13T15:18:22.284Z"
}
],
"criteria": "\u2018wordpress.comments\u2019 is greater than threshold of 5"
}
],
"text": "ALERT: Wordpress\n\n- \u2018wordpress.comments\u2019 is greater than threshold of 5 for ip-172-31-18-138 (all, wordpress) since Mon Jun 13 2016 15:18:22 GMT+0000 (UTC)\n\n Please login (https:\/\/app.dataloop.io) to your account (default) to investigate.",
"description": "ALERT: Wordpress\n\n- \u2018wordpress.comments\u2019 is greater than threshold of 5 for ip-172-31-18-138 (all, wordpress) since Mon Jun 13 2016 15:18:22 GMT+0000 (UTC)\n\n Please login (https:\/\/app.dataloop.io) to your account (default) to investigate.",
"message": "ALERT: Wordpress\n\n- \u2018wordpress.comments\u2019 is greater than threshold of 5 for ip-172-31-18-138 (all, wordpress) since Mon Jun 13 2016 15:18:22 GMT+0000 (UTC)\n\n Please login (https:\/\/app.dataloop.io) to your account (default) to investigate.",
"host": "ip-172-31-18-138"
}
This payload is parsed by Jira Service Management as:
JSON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
[
"event" : "ALERT",
"event_type" : "trigger",
"host" : "ip-172-31-18-138",
"rule" : "Wordpress",
"text" : "Alert Text",
"entity_id" : "572eb7099b36dd8ef71f3f61",
"triggers" : "Triggers:
Sources:
Name: ip-172-31-18-138
Tags: all,wordpress
Timestamp: 2016-06-13T15:18:22.284Z
Criteria: ‘wordpress.comments’ is greater than threshold of 5
",
"account" : "default",
]
Close Alert payload:
JSON
1
2
3
4
5
6
7
8
9
10
11
{
"event": "RECOVERED",
"rule": "Wordpress",
"account": "default",
"event_type": "resolve",
"entity_id": "572eb7099b36dd8ef71f3f61",
"text": "RECOVERED: Wordpress\n",
"description": "RECOVERED: Wordpress\n",
"message": "RECOVERED: Wordpress\n",
"host": ""
}
Was this helpful?