Get started with Opsgenie as a user
Learn how to configure your profile, get notifications from Opsgenie and view on-call schedules.
Integrate Opsgenie with LogicMonitor
Overview
Deploy and manage monitoring tools faster and automatically with AutoDiscovery of devices. Act on infrastructure performance data using built-in and customizable dashboards, performance forecasting, and complete reporting. Use built-in workflow capabilities, including alerting routing and escalation management, to improve the IT team’s issue response and resolution time. Forward LogicMonitor alerts to Opsgenie to notify users via iPhone and Android push notifications, email, SMS, and phone calls, track the alert lifecycle, escalate alerts, etc.
What does the integration offer?
Opsgenie has a native, bidirectional integration with LogicMonitor. Use the integration to automatically sync LogicMonitor with Opsgenie alerts and benefit from Opsgenie’s rich alert notification system, escalations, and on-call rotations.
This document describes the basic functionality of the integration, how to configure it, and the details of data exchanged between Opsgenie and LogicMonitor.
How does the integration work?
When an alert is created in LogicMonitor, an alert is also created in Opsgenieautomatically through the integration.
When an alert is closed in LogicMonitor, a related alert is also closed in Opsgenie.
When an alert is acknowledged in LogicMonitor, a related alert is also acknowledged in Opsgenie.
When the alert is acknowledged by in Opsgenie, a related alert is acknowledged automatically in LogicMonitor as well.
Set up the integration
LogicMonitor is a bidirectional integration. Setting it up involves the following steps:
Add a LogicMonitor integration in Opsgenie
Configure the integration in LogicMonitor
Add a LogicMonitor 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.
To add a LogicMonitor integration in Opsgenie:
Go to Settings > Integrations.
Select Add integration.
Run a search and select “LogicMonitor”.
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 integration URL, which includes the Opsgenie endpoint and the API key.
You will use this URL while configuring the integration in LogicMonitor later.Select Send alert updates back to LogicMonitor to send alert actions in Opsgenie to LogicMonitor.
If the box is selected, then fill in the related fields. It might be a good idea to create a user in LogicMonitor that only has an "ackonly" role for sending alert actions from Opsgenie to LogicMonitor.Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.
Configure the integration in LogicMonitor
In LogicMonitor, select Settings > Integrations.
Search for LogicMonitor and select Add > Custom HTTP Delivery.
Replace http://www.example.com/uri with the URL you copied while adding the integration in Opsgenie.
Update Alert Data with the contents of alertData.txt.
Select “Form Data” for the Data Format.
Select Submit.
Sample payloads sent from LogicMonitor
(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
{
"alertid": "LMS22",
"alertstatus": "active",
"datasource": "WinVolumeUsage-C:\",
"datapoint": "PercentUsed",
"date": "2014-05-02 14:21:40 PDT",
"dsdesc": "Monitors space usage on logical volumes.",
"dsidesc": null,
"datapointdesc": "Percentage Used on the volume",
"group": "group1,group2",
"host": "opsgenie-test-server",
"hostdesc": "Server used for testing OpsGenie integrations",
"instance": "C:\",
"level": "warning",
"duration": "1465",
"threshold": "10",
"eventsource": "WinVolumeUsage-C:\",
"eventlogfile": "Application",
"eventtype": "information",
"eventmsg": "Percentage used on the volume exceeded 80%",
"eventlogmsg": "Remaining capacity(1456750MB) of volume C:\ is lower than 25%",
"eventcode": "1847502394",
"eventuser": "test-user",
"value": "83",
"batchdesc": "Monitors space usage on logical volumes everyday.",
"hostips": "123.456.789.012",
"hosturl": "https://opsgenie-test-server.net/",
"service": "webservice",
"alerttype": "error",
"agent": "opsgenie-test-server",
"checkpoint": "1879234",
"hostinfo": null,
"servicedetail": null,
"serviceurl": "https://opsgenie-test-server.net/",
"servicegroup": "Functional Testing",
"clearvalue": "1"
}
Troubleshooting test alerts
These informational alerts denote that incoming data is for testing purposes only. Since testing data could differ from the expected data, we create an alert without running the integration flow.
While processing a LogicMonitor request, we check whether it is a test request. If it is, we interrupt the integration flow (which populates the dynamic fields, etc) and create an alert request with desired parameters. If the integration field is null during processing, it's set to DefaultAPI integration (which can't be removed or guaranteed to exist). In this case, it becomes an alert created by the default API.
Was this helpful?