Get started with Opsgenie as a user
Learn how to configure your profile, get notifications from Opsgenie and view on-call schedules.
BMC TrueSight Pulse sends notifications for alarms. With BMC TrueSight Pulse Integration, Opsgenie 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.
When an alert is created in BMC TrueSight Pulse, an alert is created in Opsgenie automatically through the integration.
If you're using Opsgenie's Free or Essentials plan or if you’re using Opsgenie with Jira Service Management's Standard plan, you can add this integration from your team dashboard only. The Integrations page under Settings is not available in your plan.
Go to Teams and select your team.
Select Integrations on the left navigation and then select Add integration.
Adding the integration from your team dashboard will make your team the owner of the integration. This means Opsgenie will assign the alerts received through this integration to your team only. Follow the rest of the steps in this section to set up the integration.
Go to Settings > Integrations. Search for Azure Event Hubs and select Add.
Specify who is notified of BMC TrueSight Pulse alerts using the Responders field. Auto-complete suggestions are provided as you type.
Copy the API Key.
Select Save Integration.
In BMC TrueSight Pulse, go to Settings -> Actions
Click "Add Action" -> Choose "opsgenie".
3. Set the Action name to Opsgenie and paste the API Key you copied before.
4. Click Save.
5. Go to Settings -> Alarms.
6. Edit an existing alarm or add a new one.
7. Under Actions add an Opsgenie action.
8. Make sure "Notify for every change" to receive notifications for each server in the group, monitored by this alarm.
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
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 Opsgenie as:
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
{
"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?