Integrate 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 Jira Service Management 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?

Jira Service Management has a native, bidirectional integration with LogicMonitor. Use the integration to automatically sync LogicMonitor with Jira Service Management alerts and benefit from Jira Service Management’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 Jira Service Management and LogicMonitor.

How does the integration work?

When an alert is created in LogicMonitor, an alert is also created in Jira Service Management automatically through the integration.
When an alert is closed in LogicMonitor, a related alert is also closed in Jira Service Management.
When an alert is acknowledged in LogicMonitor, a related alert is also acknowledged in Jira Service Management.
When the alert is acknowledged by in Jira Service Management, 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 Jira Service Management
Map alert actions
Configure the integration in LogicMonitor

Add LogicMonitor 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 LogicMonitor integration in Jira Service Management:

Go to your team’s operations page.
On the left navigation panel, select Integrations and then 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 Jira Service Management endpoint as well as the API key.
You will use this URL while configuring the integration in LogicMonitor later.
Select "Send Alert Actions to LogicMonitor" field to send alert actions in Jira Service Management 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 Jira Service Management 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 Jira Service Management
Update Alert Data with the contents of alertData.txt.
Select “Form Data” for the Data Format.
Select Submit.

Sample payloads sent from LogicMonitor

Sample payload (in JSON format)

{
        "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": "jsm-test-server",
        "hostdesc": "Server used for testing Jira Service Management 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://jsm-test-server.net/",
        "service": "webservice",
        "alerttype": "error",
        "agent": "jsm-test-server",
        "checkpoint": "1879234",
        "hostinfo": null,
        "servicedetail": null,
        "serviceurl": "https://jsm-test-server.net/",
        "servicegroup": "Functional Testing",
        "clearvalue": "1"
    }

Troubleshooting

Troubleshooting test alerts

These informational alerts denote that incoming data is for testing purposes only. Since testing data could be different from the expected data, we are directly creating an alert without running our integration flow.

While we are processing a Logic Monitor request, we check whether it is a test request or not. If it’s a test request, we interrupt the integration flow (which populate dynamic fields, etc.) and create an alert request with desired parameters (like integration, user -we set it to LogicMonitor-) but the integrations parameter themselves and while this request is processing if the integration field is null it is set to DefaultAPI integration (which can’t be removed and guaranteed to exist.) Hence, in the end, it’ll become an alert created by default API.