Introduction

This document shows an example of what needs to be done in LogicMonitor to make it integration-ready with ONEiO. The LogicMonitor endpoint currently supports integration for alerts, receiving notifications on monitoring events, and acknowledging and making notes. 

In case you have questions related to setting up the integration, send an email to support@oneio.cloud.

You can sign up for a free trial of ONEiO from the following link: ONEiO Free Trial

Overview

This article gives an overview of the required steps to integrate ONEiO and LogicMonitor. In this guide, we cover the following steps required for bi-directional communication between ONEiO and LogicMonitor.

1. Set up Integration with LogicMonitor
2. Configure LogicMonitor Alert Management

Sending messages from ONEiO to LogicMonitor

Set up Integration with LogicMonitor

To send messages from ONEiO to LogicMonitor, we need to:

1. Create an integration user
2. Generate an API Token
3. Save the above to the ONEiO endpoint

ONEiO accesses LogicMonitor through the dedicated REST API resource for managing alerts. The authentication is of a Bearer type via an API token. Before generating a token it is a good practice to create a dedicated for the integration user. Once created simply insert the user and token values into the dedicated fields in the endpoint editor:

Sending messages from LogicMonitor to ONEiO

Configure LogicMonitor Alert Management

1. Create Custom HTTP Delivery
2. Create an Escalation Chain
3. Create an Alert rule 
4. Assign the escalation chain to the alert rule

To receive messages from LogicMonitor we need to set up Custom HTTP Delivery. 

After assigning the name and selecting the desired one for the integration activities we need to define the URL via HTTPS which depends on the ONEiO environment you are working with:

QA: rest-receiver-test.service-flow.com/api

PROD: rest-receiver.service-flow.com/api 

The requests will always be sent to the same URL using HTTP Post, so you can leave those settings as default. 

Next, we should define the username and password fields. You can copy the values from the corresponding section of the endpoint in ONEiO:

As to the data, ONEiO expects it to be JSON-formatted and you can use the following template: 

{
"id": "##INTERNALID##",
"alert_id": "##ALERTID##",
"user": "##ADMIN##",
"message": "##MESSAGE##",
"type": "##ALERTTYPE##",
"status": "##ALERTSTATUS##",
"collector_id": "##AGENTID##"
}

or/and add the necessary integration tokens manually. For the integration to function properly it is recommended to assign the “id” key with the “##INTERNALID##” token. 

Once done, there is a handy “Test Aler Delivery” function that allows you to verify your connection with ONEiO is functional. If successful you will receive the ONEiO transaction Id in response:

and will be able to see the message in the feed:

Ultimately to start receiving alert information in your subscription we need to create an escalation chain and assign it to the desired alert rule. As recommended by LogicMonitor it is best to use a dedicated user as the recipient (which we already created for the outbound part). Then it is simply a matter of selecting the custom HTTP delivery as a contact.

Once configured you should start receiving messages about the alerts matching the desired alert rules with our integration as the escalation chain.