Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Integrate with Evident.io
This article highlights a new alerting feature that's natively available in Jira Service Management which is gradually rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.
What does the integration offer?
Use Jira Service Management's Evident.io Integration to forward Evident.io alerts to Jira Service Management. Jira Service Management determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls and iOS & Android push notifications, and escalates alerts until the alert is acknowledged or closed.
How does the integration work?
When a signature is created in Evident.io, an alert is created in Jira Service Management automatically through the integration.
Set up the integration
Evident.io is an API-based integration. Setting it up involves the following steps:
Add an Evident.io integration in Jira Service Management
Configure the integration in Evident.io
Add an Evident.io integration
If you're using the Free or Standard plan in Jira Service Management, you can only add this integration from your team’s operations page. To access the feature through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be on Premium or Enterprise plan.
Adding an integration from your team’s operations page makes your team the owner of the integration. This means Jira Service Management only assigns the alerts received through this integration to your team.
To add an Evident.io integration in Jira Service Management, complete the following steps:
Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “Evident.io”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.Expand the Steps to configure the integration section and copy the API URL.
You will use this URL while configuring the integration in Evident.io later.Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.
Configure the integration in Evident.io
To configure the integration of Evident.io with Jira Service Management, complete the following steps:
In Evident.io, go to Control Panel > Integrations.
Select Webhook.
Paste the API URL copied previously from Jira Service Management into URL.
Enter the maximum number of alerts that may be sent through this integration every minute into Throttle Rate.
Check the alert types and signatures to receive.
Select Submit.
Fill in the Integration Configuration form.
Select Save.
Sample webhook message from the Evident.io Plugin
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
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
{
"data": {
"id": "259835974",
"type": "alerts",
"attributes": {
"created_at": "2016-11-08T12:46:55.000Z",
"status": "pass",
"resource": "jsm-app",
"updated_at": "2016-11-09T09:45:04.000Z",
"started_at": "2016-11-08T12:46:55.000Z",
"ended_at": null
},
"relationships": {
"external_account": {
"data": {
"id": "4055",
"type": "external_accounts"
},
"links": {
"related": "https://esp.evident.io/api/v2/external_accounts/4055.json"
}
},
"region": {
"data": {
"id": "9",
"type": "regions"
},
"links": {
"related": "https://esp.evident.io/api/v2/regions/9.json"
}
},
"signature": {
"data": {
"id": "136",
"type": "signatures"
},
"links": {
"related": "https://esp.evident.io/api/v2/signatures/136.json"
}
},
"custom_signature": {
"data": null,
"links": {
"related": null
}
},
"suppression": {
"data": null,
"links": {
"related": null
}
},
"metadata": {
"data": {
"id": "258238708",
"type": "metadata"
},
"links": {
"related": "https://esp.evident.io/api/v2/alerts/259835974/metadata.json"
}
},
"cloud_trail_events": {
"data": [],
"links": {
"related": "https://esp.evident.io/api/v2/alerts/259835974/cloud_trail_events.json"
}
},
"tags": {
"data": [],
"links": {
"related": "https://esp.evident.io/api/v2/alerts/259835974/tags.json"
}
}
}
},
"included": [
{
"id": "4055",
"type": "external_accounts",
"attributes": {
"created_at": "2016-11-08T12:28:31.000Z",
"name": "Jira Service Management Development",
"updated_at": "2016-11-09T06:26:22.000Z",
"arn": "arn:aws:iam::729181177740:role/Evident-Service-Role",
"account": "729181177740",
"external_id": "960f0836-b71f-45d3-a54f-4cf1608804c7",
"cloudtrail_name": null
},
"relationships": {
"organization": {
"links": {
"related": "https://esp.evident.io/api/v2/organizations/1874.json"
}
},
"sub_organization": {
"links": {
"related": "https://esp.evident.io/api/v2/sub_organizations/3426.json"
}
},
"team": {
"links": {
"related": "https://esp.evident.io/api/v2/teams/4000.json"
}
},
"scan_intervals": {
"links": {
"related": "https://esp.evident.io/api/v2/external_accounts/4055/scan_intervals.json"
}
}
}
},
{
"id": "9",
"type": "regions",
"attributes": {
"code": "global",
"created_at": "2014-06-05T23:42:37.000Z",
"updated_at": "2014-06-05T23:42:37.000Z"
}
},
{
"id": "136",
"type": "signatures",
"attributes": {
"created_at": "2016-09-07T16:30:14.000Z",
"description": "\"IAM users can access AWS resources using different types of credentials, such as passwords or access keys. Best security practice is to remove or deactivate any credentials that have been unused in the last 90 days. Disabling or removing unnecessary credentials will reduce the window of opportunity for credentials associated with a compromised or abandoned account to be used. This signature scans for any such incidents and generates a report if one is discovered.\"",
"identifier": "AWS:IAM-014",
"name": "Unused IAM User Credentials",
"resolution": "\"To resolve this alert:Open the AWS IAM Console. Go to Users, select the user identified in the alert.Select the Security Credentials tab.Click Manage Password.Click Remove Existing Password to prevent the user from logging in until their credentials can be verified.For more information: see AWS: IAM documentation.\"",
"risk_level": "Low",
"updated_at": "2016-11-01T17:17:43.000Z"
},
"relationships": {
"service": {
"links": {
"related": "https://esp.evident.io/api/v2/services/4.json"
}
}
}
},
{
"id": "258238708",
"type": "metadata",
"attributes": {
"data": {
"details": {
"arn": "arn:aws:iam::729181177740:user/jsm-app",
"message": "User has logged in in the past 90 days",
"username": "jsm-app"
}
}
}
}
]
}
Was this helpful?