Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Integrate with BMC TrueSight Pulse
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?
BMC TrueSight Pulse sends notifications for alarms. With BMC TrueSight Pulse Integration, Jira Service Management acts as a dispatcher for these alarms, determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls and iPhone & Android push notifications, and escalates alerts until the alert is acknowledged or closed.
How does the integration work?
When an alert is created in BMC TrueSight Pulse, an alert is created in Jira Service Management automatically through the integration.
Set up the integration
BMC TrueSight Pulse is an API integration. Setting it up involves the following steps:
Add a BMC TrueSight Pulse integration in Jira Service Management
Configure the integration in BMC TrueSight Pulse
Add a BMC TrueSight Pulse 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 a BMC TrueSight Pulse 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 “BMC TrueSight Pulse”.
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 key.
You will use this key while configuring the integration in BMC TrueSight Pulse 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 BMC TrueSight Pulse
To configure the integration of BMC TrueSight Pulse with Jira Service Management, complete the following steps:
Go to Settings > Actions.
Select Add Action and then Jira Service Management.
Enter “Opsgenie” for Name.
Paste the API key you copied earlier into API Key.
Select Save.
Go to Settings > Alarms.
Add a new alarm or edit an existing one.
Under Actions, add an Opsgenie action.
Select Notify for every change to receive notifications for each server in the group monitored by the alarm.
Sample payload sent from BMC TrueSight Pulse
Create Alert payload (in JSON format)
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
{
"alarmName": "CPU usage is high",
"status": "TRIGGERED",
"metric": {
"id": "cpu",
"name": "CPU utilization",
"type": "percent"
},
"affectedServers": {
"boundary": {
"isSet": true,
"hostname": "boundary",
"aggregate": "avg",
"metric": "CPU utilization",
"value": 0.027916727272727274,
"threshold": 0.02,
"time": 1421887800000,
"link": "https://premium.boundary.com/home/1829/standard?ival=60&marker=1421887800000!cpu",
"text": {
"isSet": true,
"serverName": "boundary",
"link": "https://premium.boundary.com/home/1829/standard?ival=60&marker=1421887800000!cpu",
"labelHTML": "Server boundary's avg CPU utilization is 2.8% which is greater than the threshold of 2.0%",
"labelText": "Server boundary's avg CPU utilization is 2.8% which is greater than the threshold of 2.0%"
}
}
},
"boundary2": {
"isSet": true,
"hostname": "boundary2",
"aggregate": "avg",
"metric": "CPU utilization",
"value": 0.027916727272727274,
"threshold": 0.02,
"time": 1421887800000,
"link": "https://premium.boundary.com/home/1829/standard?ival=60&marker=1421887800000!cpu",
"text": {
"isSet": true,
"serverName": "boundary2",
"link": "https://premium.boundary.com/home/1829/standard?ival=60&marker=1421887800000!cpu",
"labelHTML": "Server boundary's label",
"labelText": "Server boundary's avg CPU utilization is 2.8% which is greater than the threshold of 2.0%"
}
},
"resolvedServers": {
"boundary": {
"isSet": false,
"hostname": "boundary",
"aggregate": "avg",
"metric": "CPU utilization",
"value": 0.004986516666666667,
"threshold": 0.02,
"time": 1421887380000,
"text": {
"isSet": false,
"serverName": "boundary",
"labelHTML": "Server boundary's avg CPU utilization has returned to the acceptable 0.5%",
"labelText": "Server boundary's avg CPU utilization has returned to the acceptable 0.5%",
"link": "https://premium.boundary.com/home/1829/standard?ival=60&marker=1421887380000!cpu"
}
}
}
}
This payload is parsed by Jira Service Management as follows:
(in JSON format)
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
{
"alarmName": "CPU usage is high",
"status": "TRIGGERED",
"metricId": "cpu",
"metricName": "CPU utilization",
"type": "percent",
"affectedServers": {
"boundary": {
"isSet": true,
"hostname": "boundary",
"aggregate": "avg",
"metric": "CPU utilization",
"value": 0.027916727272727274,
"threshold": 0.02,
"time": 1421887800000,
"link": "https://premium.boundary.com/home/1829/standard?ival=60&marker=1421887800000!cpu",
"text": {
"isSet": true,
"serverName": "boundary",
"link": "https://premium.boundary.com/home/1829/standard?ival=60&marker=1421887800000!cpu",
"labelHTML": "Server boundary's avg CPU utilization is 2.8% which is greater than the threshold of 2.0%",
"labelText": "Server boundary's avg CPU utilization is 2.8% which is greater than the threshold of 2.0%"
}
}
},
"resolvedServers": {
"boundary": {
"isSet": false,
"hostname": "boundary",
"aggregate": "avg",
"metric": "CPU utilization",
"value": 0.004986516666666667,
"threshold": 0.02,
"time": 1421887380000,
"text": {
"isSet": false,
"serverName": "boundary",
"labelHTML": "Server boundary's avg CPU utilization has returned to the acceptable 0.5%",
"labelText": "Server boundary's avg CPU utilization has returned to the acceptable 0.5%",
"link": "https://premium.boundary.com/home/1829/standard?ival=60&marker=1421887380000!cpu"
}
}
}
}Was this helpful?